agent-embassy

Agent ID — Issue

agentid_issue

Idempotent

Use agentid_issue when you want to issue an Agent ID: a signed identity attestation binding an agent's public key to a verified accountable principal, with operator details and an expiry. Issuance is refused when the principal cannot be verified — that refusal is what makes the ID worth anything. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/issue.

Input Schema

TableJSON Schema

Name	Required	Description
`agent_pubkey`	Yes	The agent's public key (hex), the root of the Agent ID
`principal_id`	Yes	ID of the accountable principal on file with the Embassy
`operator_name`	Yes	Public name of the operator running the agent (max 200 chars)
`validity_days`	No	Days until the Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted
`principal_kind`	Yes	Kind of principal: human or legal_entity
`idempotency_key`	Yes	Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.
`principal_label`	Yes	Public label for the principal
`agent_key_scheme`	No	Key scheme for agent_pubkey: eip191 or ed25519 (default eip191)
`operator_contact`	Yes	Public contact for the operator (max 320 chars)
`principal_attestation_method`	Yes	How the Embassy verified the principal

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. verified_check
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.15"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / agent_wallet

Removed value: -{
-  "description": "Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization.",
-  "type": "string"
-}

changedInput schema / properties / idempotency_key / description

Previous value: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."

Changed11 schema fields changedSep 24, 2026

addedInput schema / properties / agent_key_scheme / description

Added value: +"Key scheme for agent_pubkey: eip191 or ed25519 (default eip191)"

addedInput schema / properties / agent_pubkey / description

Added value: +"The agent's public key (hex), the root of the Agent ID"

changedInput schema / properties / agent_wallet / description

Previous value: -"dev mode only"New value: +"Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization."

addedInput schema / properties / idempotency_key / description

Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."

addedInput schema / properties / operator_contact / description

Added value: +"Public contact for the operator (max 320 chars)"

addedInput schema / properties / operator_name / description

Added value: +"Public name of the operator running the agent (max 200 chars)"

addedInput schema / properties / principal_attestation_method / description
```
Added value: +"How the Embassy verified the principal"
```

addedInput schema / properties / principal_id / description

Added value: +"ID of the accountable principal on file with the Embassy"

addedInput schema / properties / principal_kind / description
```
Added value: +"Kind of principal: human or legal_entity"
```
addedInput schema / properties / principal_label / description
```
Added value: +"Public label for the principal"
```

addedInput schema / properties / validity_days / description

Added value: +"Days until the Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted"

AddedSep 23, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (idempotentHint=true, destructiveHint=false), the description discloses meaningful runtime behavior: issuance is refused when the principal cannot be verified, it is a paid $0.25 tool, it requires an x402 v2 PAYMENT-SIGNATURE header, and the payload must be POSTed as JSON. This adds real behavioral context beyond the generic hint flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then provides the essential payment, transport, and refusal behavior without padding. The last sentence crams cost, network info, and URL together, but it remains compact and every sentence carries useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid identity-issuance tool with a rich schema and an output schema, the description covers the critical operational facts: refusal behavior, cost, payment network, transport method, and endpoint. It does not spell out x402 setup prerequisites, but the linked documentation and payment details are sufficient context for an agent to proceed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already explains all 10 parameters. The description adds only high-level summaries like 'operator details and an expiry' rather than new per-parameter semantics. This matches the baseline of 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'issue an Agent ID: a signed identity attestation binding an agent's public key to a verified accountable principal.' This clearly separates issuance from the sibling operations renew, revoke, and verify, and states the core output without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The first sentence gives explicit guidance: 'Use agentid_issue when you want to issue an Agent ID.' It provides clear context and the main condition for use. It does not explicitly name alternatives or exclusions, but the sibling set makes the intended choice obvious enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-embassy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.