Skip to main content
Glama

Agent Embassy

by pro.aemb
OverviewDiscussionsAdmin

Server Details

Agent Embassy. https://aemb.pro

Agents pay for work and prove what happened.

Ownership verified
Status
Healthy
Uptime
99.7% over 25 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

B3.3/5.0

Scored across 24 tools

Disambiguation2/5

Several clusters overlap heavily: assurance_check, preflight_check, and trust_report all return a go/no-go trust verdict on a provider/endpoint, while ping, prove_it, proveit_verified_check, watch, diligence_pack, and cert all perform URL/document verification. Detailed descriptions help, but an agent could easily pick the wrong 'prove it' or 'trust check' tool, and the prove_it vs proveit_verified_check pair is genuinely ambiguous.

Naming Consistency2/5

Naming is snake_case throughout but stylistic conventions are mixed: prefixed verb sets (agentid_issue, compute_history), bare nouns (attest, cert, give, watch), and irregular pairs like prove_it versus proveit_verified_check. The prove/proveit split is a clear inconsistency that undermines predictability.

Tool Count3/5

24 tools is on the heavy end, though the server genuinely spans several distinct service lines (identity, trust checks, compute markets, URL proofs, social kits, content). Still, it reads as a grab-bag rather than a tightly scoped surface, so the count is borderline rather than well-sized.

Completeness3/5

Sub-domains like Agent ID (issue/renew/revoke/verify) and compute markets (spot/history/alerts) are reasonably covered, but the overall purpose is diffuse and some lifecycle operations (e.g. listing or managing issued IDs, recovery blob retrieval) are absent. Coverage is adequate for headline flows but not exhaustive.

Available Tools

25 tools
agentid_issueAgent ID — Issue
Idempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
agent_pubkeyYesThe agent's public key (hex), the root of the Agent ID
principal_idYesID of the accountable principal on file with the Embassy
operator_nameYesPublic name of the operator running the agent (max 200 chars)
validity_daysNoDays until the Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted
principal_kindYesKind of principal: human or legal_entity
idempotency_keyYesIdempotency 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_labelYesPublic label for the principal
agent_key_schemeNoKey scheme for agent_pubkey: eip191 or ed25519 (default eip191)
operator_contactYesPublic contact for the operator (max 320 chars)
principal_attestation_methodYesHow the Embassy verified the principal

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
agentid_renewAgent ID — Renew
DestructiveIdempotent
Inspect

Use agentid_renew to renew an Agent ID: a fresh Agent ID, same identity chain, new expiry; old one retired. revocation_signature over agent-id-revoke:<OLD_agent_id> (64-char lowercase ID) — same contract as retiring: EIP-191 personal_sign (envelope required; raw ECDSA fails), 0x 65-byte hex; or ed25519 nacl.sign.detached, 64-byte hex. Signer: principal or Embassy-for-cause. 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/renew.

ParametersJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected
validity_daysNoDays until the renewed Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted
idempotency_keyNoOptional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated.
revocation_signatureYesHex signature over the exact UTF-8 message agent-id-revoke:<OLD_agent_id> (64-char lowercase ID, no trailing newline) — the signature covers the OLD Agent ID being retired. EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECDSA will not verify), 0x 65-byte hex r||s||v (v=27/28). ed25519: nacl.sign.detached over the message bytes, 64-byte hex. Signer: the principal's on-file revocation key, or the Embassy signer for cause

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
agentid_revokeAgent ID — Revoke
DestructiveIdempotent
Inspect

Use agentid_revoke to retire an Agent ID instantly. revocation_signature: hex signature over the message agent-id-revoke:<agent_id> (64-char lowercase ID). EIP-191: personal_sign the message string (envelope required; raw ECDSA fails), 0x 65-byte hex, matched to the principal's revocation key. ed25519: nacl.sign.detached, 64-byte hex. Signer: principal or Embassy-for-cause. 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/revoke.

ParametersJSON Schema
NameRequiredDescriptionDefault
reasonYesWhy the Agent ID is being retired (required, max 500 characters)
agent_idYesThe Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected
idempotency_keyNoOptional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated.
revocation_signatureYesHex signature over the exact UTF-8 message agent-id-revoke:<agent_id> (64-char lowercase ID, no trailing newline). EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECDSA will not verify), 0x 65-byte hex r||s||v (v=27/28). ed25519: nacl.sign.detached over the message bytes, 64-byte hex. Signer: the principal's on-file revocation key, or the Embassy signer for cause

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
agentid_verifyAgent ID — Verify
Idempotent
Inspect

Use agentid_verify when you want to check an Agent ID's current standing: valid, revoked, expired, or unknown. Every status returns the identical response shape — the Agent ID, expiry, the full identity chain, an inclusion record, and the signed attestation envelope. Unknown IDs report unknown; never an error. 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/verify.

ParametersJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe Agent ID string returned at issuance (64 hex characters; case-insensitive). Rate-limited: 30 checks/min per client IP, 429 on exhaustion
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
assurance_checkAssurance Check
Idempotent
Inspect

Use assurance_check for a go/no-go before your agent acts on a provider. Give the provider endpoint, the planned action, the amount at stake, and the permissions requested. We probe unpaid and return a signed ALLOW, ALLOW_WITH_RESTRICTIONS, ASK_HUMAN, REVERIFY, REROUTE, or QUARANTINE decision (or UNVERIFIED). Envelope only: trust_report. Cost and policy: preflight_check. 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/assurance/check.

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYesThe action the agent intends to take, e.g. 'transfer' (required, max 200 chars)
contextNoOptional free-text context for the assessment (truncated to 2000 chars)
amount_usdcYesAmount at stake, as a positive decimal string, e.g. '0.25'
idempotency_keyYesIdempotency 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.
provider_endpointYesHTTPS URL of the provider to assess (max 2000 chars; no credentials in URL)
permissions_requestedYesPermissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
attestAttest
Idempotent
Inspect

Use attest when you want the Embassy to notarize your work: submit evidence of work done anywhere, we verify it and mint a portable signed receipt. 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 — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/attest.

ParametersJSON Schema
NameRequiredDescriptionDefault
evidence_hashNoSHA256 of work artifact
evidence_urlsNoURLs proving the work
idempotency_keyYesIdempotency 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.
work_descriptionYesWhat was done

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
certCert
Idempotent
Inspect

Use cert when the subject is a document, not a URL: give only its SHA256 hash — the document itself never leaves you, nothing is fetched and no page is checked — and get the hash timestamped in a signed, hash-chained attestation proving the document existed at that moment. For anything involving a live URL, use ping or prove_it instead. 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/cert.

ParametersJSON Schema
NameRequiredDescriptionDefault
document_hashYesSHA256 hash of your document as 64 lowercase hex characters
document_nameNoOptional label for your document (max 200 chars)
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
compute_alertsCompute Alerts
Idempotent
Inspect

Use compute_alerts when you want to know when GPU spot prices made a significant move: returns the current price-move alert list, sealed into your signed receipt. 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/markets/compute/alerts.

ParametersJSON Schema
NameRequiredDescriptionDefault
gpuNoOptional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for all GPUs
limitNoMax alerts to return; integer 1-50. Defaults to 25
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
compute_historyCompute History
Idempotent
Inspect

Use compute_history when you need GPU compute market history: a bounded time series of per-GPU cheapest/median/offer counts — or whole-market history when no GPU is named — sealed into your signed receipt. Prices are ephemeral asks, never delivered-cost guarantees. 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/markets/compute/history.

ParametersJSON Schema
NameRequiredDescriptionDefault
gpuNoOptional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for whole-market history
limitNoMax history points to return; integer 1-200. Defaults to 50
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
compute_spot_pricesCompute Spot PricesAInspect

One timestamped snapshot of observed GPU asks, not quotes — listings may be gone when you rent. Observes only; never rents, reserves, or holds. Omit gpu for the per-class snapshot. Default type ondemand; use bid for the interruptible spot auction. GET the paid_url with an x402 v2 PAYMENT-SIGNATURE header carrying the USDC authorization. Paid tool — $0.25 per snapshot, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/markets/compute/spot.

ParametersJSON Schema
NameRequiredDescriptionDefault
gpuNoOptional GPU model filter, e.g. 'H100 SXM'
typeNoOffer type: ondemand (fixed price), bid (interruptible auction — shown price is the bid floor), or reserved (longer commitment)
max_gpusNoMaximum GPU count per offer; integer 1..64
min_gpusNoMinimum GPU count per offer; integer >= 1
verifiedNoWhen true, only verified hosts; when false, only unverified hosts
max_resultsNoMax offers to return; integer 1-25
min_reliabilityNoMinimum host reliability 0..1 (inclusive); hosts below it are excluded

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: GET the paid_url with an x402 v2 PAYMENT-SIGNATURE header carrying the USDC authorization
toolYesTool name: compute_spot_prices
assetYesSettlement asset
priceYesExact price, e.g. "$0.25"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to GET (with query params) for the market snapshot
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

TDQS

A4.3/5.0
Behavior5/5

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

The description carries behavior the annotations do not: this is a paid call ($0.25 per snapshot, USDC on Base or Arbitrum One), requires an x402 v2 PAYMENT-SIGNATURE header to GET the paid URL, returns a point-in-time snapshot whose listings may already be gone, and explicitly performs no rent/reserve/hold action. With annotations silent on cost and auth, this is exactly the disclosure an agent needs.

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?

Front-loaded with the return semantics, then boundaries, then payment mechanics. Dense and mostly waste-free, though the two payment sentences overlap ('Paid tool — $0.25 per snapshot...' and 'Paid URL: https://...') in a way that could be tightened.

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

Completeness5/5

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

With an output schema present, the description needn't explain return shape, and for a 7-param, zero-required tool it still covers scope, defaults, cost, auth header, and interaction boundaries. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds semantics not in the schema: the default for type (ondemand) is unstated in the schema, and 'Omit gpu for the per-class snapshot' tells the agent what a missing filter actually returns. That is genuine value beyond the field descriptions.

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

Purpose4/5

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

States a specific verb+resource: 'One timestamped snapshot of observed GPU asks,' and sharpens it with 'not quotes — listings may be gone when you rent.' An agent immediately knows this is a read of live GPU price listings. It does not, however, contrast itself with the nearby compute_history / compute_alerts siblings, so differentiation is left implicit.

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?

Gives real conditional guidance: 'Omit gpu for the per-class snapshot' and 'Default type ondemand; use bid for the interruptible spot auction.' It also draws a firm boundary — 'Observes only; never rents, reserves, or holds.' Missing is any explicit when-to-use-this-vs-a-sibling routing (e.g. vs compute_history), which is the only gap.

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

correct_copyCorrect Copy
Idempotent
Inspect

Use correct_copy when you want a $25 correction pass over draft copy: transforms the text into your chosen voice register, normalizes formatting, verifies every link is alive, confirms your required terms appear, and scans for black-box leaks — then returns the corrected copy with a verification report and a signed receipt. You pay for the pass, never the method. 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 — $25.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/copy/correct.

ParametersJSON Schema
NameRequiredDescriptionDefault
draftYesThe raw draft copy to correct (1-20000 chars)
linksNoHTTPS URLs the copy references; each is verified alive via HEAD (fallback GET), 8s timeout, redirects never followed (max 20)
registerYesVoice register: founder-notes, elite, force, or bright
required_termsNoTerms that must appear in the final copy (max 20; each term max 100 chars; counted case-insensitively)
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
diligence_packDiligence Pack
Idempotent
Inspect

Use diligence_pack for a high-stakes decision — acquisition, partnership, large commitment — when you want every check in one call. Give a URL (optionally a document hash): one call runs liveness, content, TLS fingerprint, x402 trust verdict, and document timestamp into one signed Outcome Receipt. One check only? Buy it alone: ping, prove_it, trust_report, cert. 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 — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/diligence/pack.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL to run the full suite against
document_hashNoSHA256 of document to timestamp
document_nameNoLabel for the document
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
farcaster_kitFarcaster Kit
Idempotent
Inspect

Get an agent onto Farcaster for $0.25: the primed 7-step machine guide — fund via bridge, register the FID (+1 storage), Ed25519 signer, on-chain add (exact EIP-712 SignedKeyRequest domain), fname claim (exact UserNameProof domain), profile, publish. Every trap — earned ourselves (FID 3353330, chain fees about fifty cents, no phone/KYC). Your keys; custody never leaves you. POST 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/kits/farcaster.

ParametersJSON Schema
NameRequiredDescriptionDefault
idempotency_keyYesClient-generated UUID v4, one per logical request. Replaying the same key on the same tool returns the original receipt.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
giveGive — Support the Embassy
Idempotent
Inspect

Support the Embassy. An open-amount patronage gift in USDC: you choose any amount from $0.01 to $222.00; the signed 402 quote binds your exact amount and the receipt is a patronage receipt, not a work receipt. 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 — open amount, buyer chooses $0.01–$222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/give.

ParametersJSON Schema
NameRequiredDescriptionDefault
amount_usdYesExact gift amount in USD, caller-supplied: a plain decimal string like "5.00" ("$5.00" also accepted) or a number with at most 2 decimals. Canonical integer-cent parse: exponent, locale/grouping, sub-cent precision, negative, zero, below-$0.01 and above-$222.00 forms are rejected. The signed 402 quote binds this exact amount; you authorize exactly what you quoted.
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
nostr_kitNostr Kit
Idempotent
Inspect

Get an agent onto Nostr for $0.25: the primed 4-step machine guide — secp256k1 keygen with verified bech32 derivation, per-relay NIP-11 policy reads before publishing, NIP-01 canonical event signing, publish order (relay list → profile → note) with per-relay acceptance proof. No chain fees, no signup, no recovery — the nsec backup rules included. Earned from our live presence. POST 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/kits/nostr.

ParametersJSON Schema
NameRequiredDescriptionDefault
idempotency_keyYesClient-generated UUID v4, one per logical request. Replaying the same key on the same tool returns the original receipt.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
pingPing
Idempotent
Inspect

Use ping when you define the test: give a URL plus your expectations — HTTP status (default 200), a required body substring, and/or an exact value at one JSON path — and get a per-condition pass/fail verdict from one fetch in a signed receipt. prove_it instead fixes the test at HTTP 200 and seals the transcript for others. For change alerts over time: watch. 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.05, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/check/ping.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL to check (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap
expect_statusNoExpected HTTP status code; truncated to an integer. Defaults to 200 when omitted
idempotency_keyYesIdempotency 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.
expect_json_pathNoDot-separated path into the JSON body, e.g. 'data.price' (max 500 chars). Only evaluated when set
expect_json_equalsNoExpected value at expect_json_path; compared by canonical JSON equality. Defaults to null when omitted
expect_body_containsNoSubstring that must appear in the response body (max 5000 chars). Skipped when empty or omitted

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
preflight_checkPreflight Check
Idempotent
Inspect

Use preflight_check before paying for a specific tool or server call. Name the target (server, artifact, version), the operation, the advertised cost, and your policies. Get back who is paid, what is delivered, what changed, full cost, every cut taken — a signed PROCEED, PROCEED_WITH_CAUTION, BLOCKED, or UNKNOWN verdict against your policy. Envelope only: trust_report. 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/preflight/check.

ParametersJSON Schema
NameRequiredDescriptionDefault
intentYesThe intended invocation: operation (required), params_summary (sha256 of canonical params), advertised_cost_usdc
policyNoPolicy strings (max 20)
contextNoprincipal_wallet + chain. Optional.
dry_runNotrue = free dry-run, intercepted before the payment gate
subjectYesThe spend target: server_id (required), artifact (mcpb:// | oci:// | https://), claimed_version
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
prove_itProve-It — Verified Proof Receipts for Superintelligence (x402)
Idempotent
Inspect

Use prove_it when someone else must be convinced: give one URL; one fetch is sealed into a signed Outcome Receipt with the full transcript — proof it was live and returning HTTP 200 at check time, verifiable by anyone. Fixed at 200 — your own status, substring, or JSON conditions belong to ping. No prices: proveit_verified_check is the GPU spot-price check. 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/check/prove.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL to prove live (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap. Default expectation: HTTP 200
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
proveit_verified_checkProve-It Verified Check
Idempotent
Inspect

Use proveit_verified_check to prove a GPU price observation happened — no URL is involved. Give an optional GPU class (e.g. 'H100 SXM') and offer type; we seal one timestamped spot-market snapshot (cheapest rentable ask per class, USD/hour) into a signed Outcome Receipt. Despite the name it never fetches a URL — liveness proof is prove_it; content conditions are ping. 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/check/proveit-verified.

ParametersJSON Schema
NameRequiredDescriptionDefault
gpuNoOptional GPU class, e.g. 'H100 SXM' (max 64 chars). Omit for the per-class snapshot
typeNoOffer type: ondemand, bid, or reserved. Defaults to ondemand
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
rank_the_rankersRank the RankersA
Idempotent
Inspect

Use rank_the_rankers when your agent would otherwise crawl the listing surfaces itself: one call returns the ranked directory of the agent-ranking surfaces — what each ranks, its method in one line, integrity/transparency reads, freshness, coverage, participation cost, and our standing on each — scored on published criteria, so venue choice is one read, not a sweep. 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/directory/rankers.

ParametersJSON Schema
NameRequiredDescriptionDefault
surfaceNoOptional surface slug (e.g. 'x402-list', '8004scan', 'glama') to return only that entry. Omit for the full directory
idempotency_keyYesIdempotency 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.
include_unverifiedNoInclude surfaces not yet verified by a live read (listed as unverified, never ranked). Defaults to true

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

TDQS

A4.4/5.0
Behavior5/5

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

With annotations already declaring the safety profile, the description goes well beyond them by disclosing the full payment/transport contract: POST JSON to paid_url, x402 v2 PAYMENT-SIGNATURE header, $0.25 USDC on Base or Arbitrum One, the concrete paid URL, and a docs link. This is exactly the behavioral context an agent needs to actually invoke a paid tool and is consistent with readOnlyHint=false (a receipt is produced).

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?

Two sentences, both front-loaded with the actionable lead (the trigger, then the payment mechanics). The first sentence is dense with a long enumerated list, but every element earns its place and nothing is redundant.

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

Completeness5/5

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

An output schema exists, so return values need no prose. For a paid, remote tool the description covers cost, chain, auth header, endpoint, and the reasoning for using it — an agent has everything required to invoke it correctly.

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 idempotency_key, surface, and include_unverified are already fully documented in the schema, including enum-like slug examples and replay semantics. The description adds no parameter-level meaning, so the baseline 3 applies.

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 states a specific verb and resource: one call returns the ranked directory of agent-ranking surfaces, enumerating exactly what each entry contains (what it ranks, method, integrity reads, freshness, coverage, participation cost, our standing, published scoring criteria). This is highly distinguishable from all siblings, none of which touch ranking surfaces.

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?

It gives an explicit trigger ('when your agent would otherwise crawl the listing surfaces itself') and frames the value ('venue choice is one read, not a sweep'). It doesn't name a competing tool or state exclusions, so it falls just short of a 5.

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

register_recoveryRegister Recovery
Idempotent
Inspect

Use register_recovery when you want to escrow a client-encrypted recovery blob with the Embassy: it is stored opaquely (the Embassy cannot decrypt it), queued for human operator review, and you get a signed receipt proving the stored blob's hash. 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 — $1.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/recovery/register.

ParametersJSON Schema
NameRequiredDescriptionDefault
contact_nameYesYour name or operator handle, recorded with the escrow
quorum_rulesYesThe release rules for this blob, e.g. '2-of-3 named trustees must approve release'
recovery_blobYesClient-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt
contact_handleNoOptional contact (email or handle) for the operator review
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
research_paperResearch Paper
Idempotent
Inspect

Use research_paper when you want to buy a research paper: $222 for the paper, or $444 for paper+provenance (the paper plus the corpus proof pack). Licensed to your wallet — the purchased bytes are delivered privately with a signed receipt. 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 — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/research/paper.

ParametersJSON Schema
NameRequiredDescriptionDefault
bundleNoDelivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus proof pack). Defaults to 'paper'
paper_idYesCatalog ID of the paper, e.g. 'the-discontinuity-20260922'. Unknown IDs are rejected
buyer_aliasNoOptional license display name (3-32 chars: letters, digits, . _ -). Defaults to the first 8 hex chars of the buyer wallet
idempotency_keyYesIdempotency 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.
prior_receipt_idNoOptional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
ticker_shelfTicker Shelf
Idempotent
Inspect

Shop an economic idea for $0.25: one delayed scan (CBOE options, Nasdaq equities) for a ticker, a head-to-head ("COMPARE two tickers"), or a theme ("BEST a theme"). Ranked expressions whose executable asks fit your budget — empty set returns WAIT, never invented — each labeled LIVE/RECENT/SNAPSHOT/UNVERIFIED, receipt signed. Quotes move; no trades placed; not investment advice. POST 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/shelf.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to shop for: "a ticker", "a ticker, $5 budget", "COMPARE two tickers", "BEST a theme, $25 budget" (max 200 chars)
max_rowsNoRows on the shelf, 3-10 (default 10)
objectiveNoconvexity (default), long-clock, fast-heat, tail, income, leveraged
budget_usdNoHard budget gate in USD (1/5/10/25/50/100 supported; omit for uncapped)
idempotency_keyYesClient-generated UUID v4, one per logical request. Replaying the same key on the same tool returns the original receipt.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
trust_reportTrust Report
Idempotent
Inspect

Use trust_report to answer one question: is this x402 endpoint's payment demand well-formed? Give its URL; we probe it unpaid (zero spend), inspect only the 402 envelope — valid x402 v2, well-formed accepts, verb gate intact — and return a signed PROCEED, VERIFY_FIRST, or DO_NOT_PAY verdict. Provider judgment: assurance_check. Purchase breakdown: preflight_check. 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/trust/report.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL of the candidate x402 endpoint to probe (max 2000 chars; no credentials in URL). Probed unpaid via GET, falling back to an empty-body POST when GET returns 404/405
idempotency_keyYesIdempotency 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.

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.
watchWatch
Idempotent
Inspect

Use watch when the question is not 'is it up now' but 'tell me when it changes.' Give a URL and a check interval (1–168 hours); we baseline now, re-check on schedule, and a signed receipt fires — and the per-fire charge applies — only when the content changes. One-time checks are ping (your conditions) and prove_it (proof for others); watch is the only standing check. 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 — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/watch.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL to watch
idempotency_keyYesIdempotency 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.
check_interval_hoursNoHours between checks

Output Schema

ParametersJSON Schema
NameRequiredDescription
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedrank_the_rankers
  2. 23 tool updates
    • Changedagentid_issue1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedagentid_renew1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedagentid_revoke1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedagentid_verify1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedassurance_check1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedattest1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedcert1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedcompute_alerts1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedcompute_history1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedcorrect_copy1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changeddiligence_pack1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedfarcaster_kit1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedgive1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changednostr_kit1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedping1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedpreflight_check1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedprove_it1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedproveit_verified_check1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedregister_recovery1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedresearch_paper1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedticker_shelf1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedtrust_report1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
    • Changedwatch1 field changed
      • changedOutput schema / properties / price / description
        Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
  3. 23 tool updates
    • Changedagentid_issue1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedagentid_renew1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedagentid_revoke1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedagentid_verify1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedassurance_check1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedattest1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedcert1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedcompute_alerts1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedcompute_history1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedcorrect_copy1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changeddiligence_pack1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedfarcaster_kit1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedgive1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changednostr_kit1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedping1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedpreflight_check1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedprove_it1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedproveit_verified_check1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedregister_recovery1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedresearch_paper1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedticker_shelf1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedtrust_report1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
    • Changedwatch1 field changed
      • changedOutput schema / properties / tool / description
        Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  4. 2 tool updates
    • Changedcompute_spot_prices2 fields changed
      • addedInput schema / properties / max_gpus
        Added value: +{
+  "description": "Maximum GPU count per offer; integer 1..64",
+  "maximum": 64,
+  "minimum": 1,
+  "type": "integer"
+}
      • changedInput schema / properties / type / description
        Previous value: -"Offer type filter: ondemand, bid, or reserved"New value: +"Offer type: ondemand (fixed price), bid (interruptible auction — shown price is the bid floor), or reserved (longer commitment)"
    • Changedproveit_verified_check1 field changed
      • changedInput schema / properties / gpu / description
        Previous value: -"Optional GPU class, e.g. 'H100 SXM' (max 64 chars). Omit for all 13 classes"New value: +"Optional GPU class, e.g. 'H100 SXM' (max 64 chars). Omit for the per-class snapshot"
  5. 6 tool updates
    • Addedattest
    • Changedcorrect_copy2 fields changed
      • changedInput schema / properties / register / description
        Previous value: -"Voice register: founder-notes, elite, force, or bright-soft-junior"New value: +"Voice register: founder-notes, elite, force, or bright"
      • changedInput schema / properties / register / enum
        Previous value: -[
-  "founder-notes",
-  "elite",
-  "force",
-  "bright-soft-junior"
-]New value: +[
+  "founder-notes",
+  "elite",
+  "force",
+  "bright"
+]
    • Addeddiligence_pack
    • Addedping
    • Removedverified_check
    • Addedwatch
  6. 2 tool updates
    • Addedfarcaster_kit
    • Addednostr_kit
  7. 1 tool update
    • Changedticker_shelf1 field changed
      • changedInput schema / properties / query / description
        Previous value: -"What to shop for: \"TST1\", \"TST1 $5\", \"TST1 long-clock\", \"COMPARE TST1 TST2\", \"BEST TESTTHEME $25\" (max 200 chars)"New value: +"What to shop for: \"a ticker\", \"a ticker, $5 budget\", \"COMPARE two tickers\", \"BEST a theme, $25 budget\" (max 200 chars)"
  8. 1 tool update
    • Addedticker_shelf
  9. 3 tool updates
    • Removedcontribute
    • Addedgive
    • Changedresearch_paper1 field changed
      • changedInput schema / properties / bundle / description
        Previous value: -"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus evidence pack). Defaults to 'paper'"New value: +"Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus proof pack). Defaults to 'paper'"
  10. 2 tool updates
    • Addedcert
    • Removednotarize
  11. 1 tool update
    • Addednotarize
  12. 1 tool update
    • Addedcontribute
  13. 15 tool updates
    • Changedagentid_issue2 fields changed
      • 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."
    • Changedagentid_renew2 fields changed
      • 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: -"Optional idempotency key: any non-empty string (a UUID is recommended; no format is enforced). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated."
    • Changedagentid_revoke2 fields changed
      • 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: -"Optional idempotency key: any non-empty string (a UUID is recommended; no format is enforced). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated."
    • Changedagentid_verify2 fields changed
      • 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."
    • Changedassurance_check1 field changed
      • 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."
    • Changedcompute_alerts2 fields changed
      • 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."
    • Changedcompute_history2 fields changed
      • 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."
    • Changedcorrect_copy2 fields changed
      • 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."
    • Changedpreflight_check2 fields changed
      • 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."
    • Changedprove_it1 field changed
      • 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."
    • Changedproveit_verified_check2 fields changed
      • 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."
    • Changedregister_recovery2 fields changed
      • 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."
    • Changedresearch_paper3 fields changed
      • 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. Keys are additionally scoped per payer account: a key never returns another wallet's receipt."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."
      • addedInput schema / properties / prior_receipt_id
        Added value: +{
+  "description": "Optional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle",
+  "type": "string"
+}
    • Changedtrust_report2 fields changed
      • 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."
    • Changedverified_check2 fields changed
      • 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."

Publisher details

Operator
Agent Embassy
Operator website
https://aemb.pro
Vendor relationship
First-party
Documentation
https://aemb.pro
Trust center
https://aemb.pro
Restrictions
Unknown

Related MCP Connectors

Related MCP Servers

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.

Resources