AGEX Signature Verifier

Verify the Ed25519 signature attached to an AGEX bundle

This tool verifies whether an AGEX bundle signature is valid. It can use the embedded public key for convenience or a separately supplied public key when you want explicit trust control.

Example Results

1 examples

Verify an AGEX bundle signature

Check whether the bundle signature matches the provided or embedded public key

{
  "result": {
    "signatureVerification": "verified",
    "signaturePresent": true
  }
}
View input parameters
{ "bundleFile": "/public/processing/example.agex.json", "signerPublicKey": "BASE64_PUBLIC_KEY" }

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, textarea
Output Type
json
Sample Coverage
4
API Ready
Yes

Overview

The AGEX Signature Verifier allows you to quickly validate the Ed25519 signature attached to an AGEX bundle. By uploading your bundle file, you can confirm its authenticity using either the embedded public key or a custom base64-encoded public key for strict trust verification, all without needing a passphrase or decrypting the file contents.

When to Use

  • •When you need to confirm that an AGEX bundle has not been tampered with and originates from a trusted sender.
  • •When you want to verify the cryptographic signature of a bundle without decrypting its payload or entering a passphrase.
  • •When you need to enforce explicit trust control by validating an AGEX bundle against a specific, externally provided Ed25519 public key.

How It Works

  • •Upload the AGEX bundle file (up to 100MB) that contains the signature you want to verify.
  • •Optionally, paste a base64-encoded Ed25519 public key into the signer public key field to enforce verification against a specific identity.
  • •Click the verify button to run the cryptographic check on the bundle's Ed25519 signature.
  • •Review the generated JSON output to confirm if the signature is present and successfully verified.

Use Cases

Verifying the integrity of received AGEX software packages or data bundles before deployment.
Auditing signed AGEX archives to ensure they match a known developer's public key.
Troubleshooting failed bundle imports by checking if the signature is present and cryptographically valid.

Examples

1. Verify Bundle Integrity with Embedded Key

DevOps Engineer
Background
A DevOps engineer received a signed AGEX configuration bundle and wants to ensure the file was not corrupted during transit.
Problem
Confirming the bundle's internal signature is valid without having the sender's public key on hand.
How to Use
Upload the AGEX bundle file to the tool, leave the Signer Public Key field blank, and run the verification.
Example Config
Signer Public Key field left blank.
Outcome
The tool returns a JSON result showing that the signature is present and verified using the embedded key.

2. Enforce Trust with a Specific Public Key

Security Auditor
Background
An auditor needs to verify that a received AGEX bundle was signed specifically by the organization's official release key, not just any embedded key.
Problem
Verifying the bundle signature against a known, trusted external public key.
How to Use
Upload the AGEX bundle file and paste the organization's base64-encoded Ed25519 public key into the Signer Public Key field.
Example Config
Signer Public Key: BASE64_PUBLIC_KEY
Outcome
The tool validates the signature against the provided key and outputs a JSON confirmation indicating a successful match.

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

Does this tool decrypt the contents of the AGEX bundle?

No, this tool only verifies the cryptographic Ed25519 signature and does not decrypt the payload or require a decryption passphrase.

What happens if I leave the Signer Public Key field blank?

The tool will automatically attempt to verify the signature using the public key embedded within the AGEX bundle itself.

What format should the external public key be in?

The external signer public key must be provided as a base64-encoded Ed25519 public key.

What file size limit applies to the AGEX bundle?

You can upload AGEX bundle files up to 100MB in size for signature verification.

How do I know if the signature verification succeeded?

The output JSON will display a 'signatureVerification' status of 'verified' if the signature is valid.

API Documentation

Request Endpoint

POST /en/api/tools/agex-signature-verifier

Request Parameters

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

File type parameters need to be uploaded first via POST /upload/agex-signature-verifier 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-signature-verifier": {
      "name": "agex-signature-verifier",
      "description": "Verify the Ed25519 signature attached to an AGEX bundle",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=agex-signature-verifier",
      "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]