An Agent Lands on Your Homepage — What Can It Actually Read?
Eleven machine-readable manifests under /.well-known plus a generated llms.txt — the full AgentBadge discovery surface is built from live…
Read more →Deep dives into agent-ready infrastructure, MCP protocol, x402 payments, and the agentic web.
Eleven machine-readable manifests under /.well-known plus a generated llms.txt — the full AgentBadge discovery surface is built from live…
Read more →
Existence proofs don't cover completeness. AgentBadge now chains every verdict (keccak256(prev ‖ artifactHash)) and anchors the head to the…
Read more →
AgentBadge now serves a machine-readable paid-services catalog at GET /api/v1/services, and every 402 response across the platform carries…
Read more →
On Arc's self-settle x402 rail the txHash is a bearer credential — public in the mempool, spendable by whoever presents it first (Attack…
Read more →
AgentBadge now has a real platform identity: did:web:agentbadge.xyz — a W3C DID anchored to our domain, a signed DID Configuration (VC-JWT…
Read more →
Refused agent-API requests should never be billed. AgentBadge publishes a machine-readable refusal contract (409/422/502/503,…
Read more →
Owner controls for agent wallets on Arc: approval holds that park a payment for a human signature, a kill-switch that evaluates before…
Read more →
One 402 response, three payment rails, one settlement chain: our agent venue accepts USDC from any Gateway-covered chain and settles on…
Read more →
Agent Wallets with spending envelopes: per-transaction, daily, weekly and monthly rolling caps on every payment an agent makes through…
Read more →