AGEX Bundle Diff

Compare two AGEX bundles and highlight metadata or protection-setting differences

This tool helps with review and audit work. It shows where two AGEX bundles differ in visible metadata, KDF presets, signer information, and low-level protection inputs such as salt, nonce, or ciphertext changes.

Example Results

1 examples

Audit what changed between two AGEX revisions

Compare the original bundle and a redistributed copy to see whether the KDF, signer label, or visible file metadata changed

{
  "result": {
    "differences": [
      {
        "field": "kdf.opslimit",
        "left": "moderate",
        "right": "sensitive"
      }
    ]
  }
}
View input parameters
{ "leftBundleFile": "/public/processing/bundle-v1.agex.json", "rightBundleFile": "/public/processing/bundle-v2.agex.json" }

Click to upload file or drag and drop file here

Maximum file size: 100MB Supported formats: application/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 Diff tool allows security auditors and developers to compare two AGEX bundles side-by-side, highlighting differences in metadata, KDF presets, signer information, and low-level protection inputs like salt, nonce, or ciphertext.

When to Use

  • •When auditing security policy changes between two versions of an AGEX bundle.
  • •When verifying if a redistributed AGEX file has altered KDF parameters or signer signatures.
  • •When troubleshooting decryption issues by checking if the ciphertext, salt, or nonce has changed.

How It Works

  • •Upload the original AGEX bundle file as the Left Bundle File.
  • •Upload the modified or comparison AGEX bundle file as the Right Bundle File.
  • •Run the comparison to generate a JSON report detailing differences in metadata fields, KDF limits, and cryptographic parameters.

Use Cases

Auditing KDF parameter changes (e.g., moderate vs. sensitive) between bundle revisions.
Verifying signer identity and signature integrity across redistributed files.
Detecting unauthorized modifications to salt, nonce, or ciphertext in a bundle.

Examples

1. Auditing Security Policy Upgrades

Security Auditor
Background
A security team upgraded their encryption policy to use stronger KDF settings for their AGEX bundles.
Problem
The auditor needs to verify that the new bundle version actually uses the 'sensitive' KDF opslimit instead of the old 'moderate' setting.
How to Use
Upload the original bundle as the Left Bundle File and the upgraded bundle as the Right Bundle File, then run the comparison.
Outcome
The tool outputs a JSON diff showing that kdf.opslimit changed from moderate to sensitive.

2. Verifying Signer Integrity

Release Engineer
Background
A release engineer is distributing an AGEX bundle and wants to ensure the signer information was not altered during transit.
Problem
Confirming that the signer ID and signature metadata match the original release bundle exactly.
How to Use
Upload the reference release bundle and the distributed bundle to compare their signer metadata.
Outcome
The comparison confirms zero differences in the signer fields, validating the bundle's integrity.

Try with Samples

json, file
Distributed Tracing Samples
Comprehensive distributed tracing examples using Jaeger, OpenTelemetry, and other modern observability tools for microservices architecture
preferred input family json
json
ELK Stack Log Analysis Samples
Comprehensive ELK Stack (Elasticsearch, Logstash, Kibana) samples for log aggregation, processing, and visualization in distributed systems
preferred input family json
json
AWS EventBridge Samples
AWS EventBridge examples including event buses, rules, targets, schema registry, custom events, and cross-account event routing for serverless event-driven architecture
preferred input family json
json
Grafana Advanced Application Samples
Comprehensive Grafana samples covering advanced dashboard design, alerting configurations, data source integrations, and plugin development
preferred input family json
json

Related Hubs

AGEX Secure File Bundle and Handoff Tools
Create encrypted AGEX bundles, inspect metadata, rotate passphrases, verify signatures, redact exposed fields, and prepare safer secure-file handoffs in one focused hub.
JSON Interchange and Format Translation Tools
Compare JSON conversion tools for CSV, YAML, TOML, GraphQL, XML, Markdown, Excel, BSON, EDN, and related structured formats in one hub.
JSON Inspection, Diff, and Transformation Tools
Compare JSON formatting, diffing, path inspection, schema validation, merging, transformation, and export tools in one hub for API and data workflows.
JSON Schema, Mock Data, and API Fixture Generators
Curated tools for JSON schema generation, mock payload building, and API fixture preparation in one hub.

FAQ

What file formats does this tool support?

It supports AGEX bundle files, typically in JSON format.

Can I detect changes in the encryption key settings?

Yes, the tool highlights differences in KDF presets, including opslimit and memlimit.

Does this tool compare the actual decrypted file contents?

No, it compares the metadata, signer information, and low-level protection inputs of the bundles.

What low-level cryptographic fields are compared?

It compares differences in salt, nonce, and ciphertext values.

Is my bundle data uploaded to a public server?

No, the comparison is processed securely to ensure your cryptographic metadata remains private.

API Documentation

Request Endpoint

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

Request Parameters

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

File type parameters need to be uploaded first via POST /upload/agex-bundle-diff 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-diff": {
      "name": "agex-bundle-diff",
      "description": "Compare two AGEX bundles and highlight metadata or protection-setting differences",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=agex-bundle-diff",
      "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]