AGEX Bundle Inspector

Inspect AGEX bundle metadata without decrypting the file contents

Use this tool when you want to understand what an AGEX bundle contains before decrypting it. It exposes only metadata such as version, file name, size, MIME type, Argon2id settings, and whether a signature block is present.

Example Results

1 examples

Inspect an AGEX bundle before decrypting

Check the bundle version, original filename, and signature presence before asking for a passphrase

{
  "result": {
    "bundleFormat": "AGEX",
    "version": 1,
    "signaturePresent": true
  }
}
View input parameters
{ "bundleFile": "/public/processing/example.agex.json" }

Click to upload file or drag and drop file here

Maximum file size: 100MB Supported formats: application/json, */*

Key Facts

Category
Security & Validation
Input Types
file
Output Type
json
Sample Coverage
4
API Ready
Yes

Overview

The AGEX Bundle Inspector allows you to safely inspect the metadata of an AGEX bundle file without decrypting its actual contents. By uploading a bundle, you can instantly view critical details such as the bundle version, original file name, size, MIME type, Argon2id key derivation parameters, and the presence of a cryptographic signature block.

When to Use

  • Before decrypting an AGEX bundle to verify its origin and integrity via the signature block.
  • When you need to check the Argon2id key derivation settings used to secure the bundle.
  • To identify the original file name, size, and MIME type of an encrypted package without entering a passphrase.

How It Works

  • Upload your AGEX bundle file using the file input field.
  • The tool parses the unencrypted header and metadata sections of the bundle structure.
  • It extracts key parameters including the bundle format version, signature status, and Argon2id configuration.
  • The extracted metadata is displayed instantly in a clean JSON format without accessing or decrypting the payload.

Use Cases

Verifying the signature status of an AGEX bundle before initiating a decryption workflow.
Auditing the Argon2id work factors (memory, iterations, parallelism) used for key derivation.
Identifying the original file extension and MIME type of an encrypted archive.

Examples

1. Verifying Signature Presence on a Received Bundle

Security Auditor
Background
An auditor receives an encrypted AGEX file from an external partner and needs to confirm it was signed before processing it.
Problem
Confirming the presence of a signature block without decrypting the payload.
How to Use
Upload the encrypted bundle file to the inspector.
Outcome
The tool outputs JSON showing signaturePresent: true and the bundle version, confirming the file is signed.

2. Checking Argon2id Parameters for Compliance

DevOps Engineer
Background
A DevOps engineer wants to ensure that the encrypted backups generated by their system use the correct Argon2id security parameters.
Problem
Verifying key derivation settings without decrypting the backup archive.
How to Use
Select the backup AGEX bundle file in the inspector.
Outcome
The tool displays the Argon2id settings, allowing the engineer to verify the memory and iteration parameters match compliance standards.

Try with Samples

json, file

Related Hubs

FAQ

Does this tool decrypt my file contents?

No, it only reads the unencrypted metadata header and does not require or accept a decryption passphrase.

What metadata fields can I inspect?

You can view the bundle format version, original file name, file size, MIME type, Argon2id parameters, and signature presence.

Is my bundle uploaded to a remote server?

No, the inspection is performed locally in your browser to ensure your metadata remains private.

What is the maximum file size supported?

The tool supports AGEX bundle files up to 100 MB in size.

Can I verify if the bundle has been digitally signed?

Yes, the inspector checks for the presence of a signature block in the bundle metadata.

API Documentation

Request Endpoint

POST /en/api/tools/agex-bundle-inspector

Request Parameters

Parameter Name Type Required Description
bundleFile file (Upload required) Yes -

File type parameters need to be uploaded first via POST /upload/agex-bundle-inspector to get filePath, then pass filePath to the corresponding file field.

Response Format

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}
JSON Data: JSON Data

AI MCP Documentation

Add this tool to your MCP server configuration:

{
  "mcpServers": {
    "elysiatools-agex-bundle-inspector": {
      "name": "agex-bundle-inspector",
      "description": "Inspect AGEX bundle metadata without decrypting the file contents",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=agex-bundle-inspector",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

Supports URL file links or Base64 encoding for file parameters.

If you encounter any issues, please contact us at [email protected]