Executable agentic-AI proof

Franklin Templeton described the category. Gregers runs the check.

Agentic AI does not just need payment rails. Before software pays, signs, or acts, the counterparty should verify the agent, wallet, policy, and receipt. This page uses the existing Gregers x402-style challenge and Concordium Agent #40 passport check to make that preflight inspectable.

Open 402 challenge Open live receipt Underlying tool gate

Proof, not category commentary

Payment proof → registry check → wallet/card-hash match → tool output → public receipt.

This is deliberately narrower than a Concordium marketing claim. It proves the accountable preflight layer Gregers can operate today.

Current status

Live

The challenge, claim, receipt, and tool-output endpoints are public. The payment is a recorded x402-style fixture; no new money moves on this page.

FTDA category → Gregers receipt

Category claim	Gregers proof object	Boundary
Machine payments	`/api/accountable-x402/challenge` returns HTTP 402-style payment requirements.	x402-style JSON fixture; not a production Cloudflare gateway integration.
Identity	Concordium Agent Registry Token #40 is checked at claim time.	Public registry check, not legal-name disclosure.
Accountability	Receipt binds agent status, wallet, agent card, metadata hash, resource, and policy.	Snapshot at claim time; later reads are historical receipts.
Audit trail	Receipt carries canonicalization rules and `receipt_hash_sha256`.	Tamper-evident public receipt, not a legal attestation.
Settlement layer	Payment evidence field records network, tx, asset, amount, and verification flags.	Recorded Base USDC fixture; fresh settlement verification is explicitly false.

Run the preflight

1 · Ask for the tool

GET /api/accountable-x402/tool

Returns 402 until a valid receipt is supplied.

2 · Claim with evidence

POST /api/accountable-x402/claim

Submits Agent #40, recorded payment evidence, resource, and policy.

3 · Inspect the receipt

GET /api/accountable-x402/receipts/<id>

Shows the payment, registry, card-hash, policy, output, and hash contract.

Copy-paste proof flow

curl -i https://gregers.dev/api/accountable-x402/tool

curl -i https://gregers.dev/api/accountable-x402/challenge

curl -s https://gregers.dev/api/accountable-x402/claim \
  -H 'content-type: application/json' \
  -d '{"agent_token_id":40,"payment_tx":"0xbf52a428e4b42bacdba0966a813c8003899697b3afdfa2dc0e6a88d1b586a18e","resource":"gregers.demo.mcp.tool.identity_digest","policy":"payment receipt + active Concordium Agent Registry passport required"}'

curl -s https://gregers.dev/api/accountable-x402/receipts/ad999ceafad40e21

What it is / is not

It is

live endpointregistry-backedhash-checkedreceipt-shaped

A concrete preflight showing why machine payments need an accountable counterparty layer.

It is not

not an FTDA endorsementnot a Cloudflare partnershipnot fresh payment settlementnot legal-name disclosure

The page keeps the boundaries explicit so Gregers can be useful without pretending to be Concordium marketing.