Skip to main content
Glama
ark-forge

ArkForge Trust Layer

by ark-forge

certify_call

Generate cryptographic proof for API calls with independent third-party signatures, timestamps, and blockchain anchoring to create auditable, tamper-evident transaction records.

Instructions

Call an external API and get a cryptographic proof of the transaction.

Use this INSTEAD of calling the API directly when you need an auditable, tamper-evident record of what was sent and received.

The proof is signed by ArkForge (independent third party), timestamped via RFC 3161, and anchored in Sigstore Rekor — not self-signed by your agent.

Args: target: URL of the upstream API to call (e.g. "https://api.example.com/v1/action") payload: JSON body to send to the upstream API (optional for GET requests) method: HTTP method — "POST" or "GET" (default: "POST") description: Human-readable description of what this call does (included in the proof) agent_identity: Identifier for the calling agent (optional, included in the proof)

Returns: JSON with proof_id, verification_url, the upstream API response, chain_hash, and timestamp. Share verification_url with any third party to let them independently verify what happened.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
payloadNo
methodNoPOST
descriptionNo
agent_identityNo
Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ark-forge/arkforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server