AgentPay

Testnet Adapter + Budget-Capped Agent Demo Add the Stacks/sBTC adapter to the public AgentPay repository; provide setup instructions for running the Stacks testnet flow; enable a testnet agent to open a budget-capped spending session; complete at least one successful testnet payment using the Stacks/sBTC path; demonstrate that the agent cannot exceed the configured spend cap; generate verifiable receipts tied to Stacks testnet transaction data; publish a public demo video or demo page; publish developer documentation covering setup, dependencies, and known limitations.

Mainnet Launch + External Validation Launch Stacks/sBTC support in the AgentPay SDK and/or MCP flow; document mainnet configuration and provide a minimal integration path for enabling Stacks/sBTC payments; complete at least one real mainnet budget-capped agent payment in sBTC; generate at least three verifiable Stacks mainnet receipts from budget-capped sBTC agent sessions; surface Stacks mainnet receipts in AgentPay’s public receipt ledger, clearly identifiable and tied to transaction/session data; demonstrate at least one rejected over-cap payment attempt with evidence of the attempted call, configured cap, rejection, and no on-chain settlement; support at least one spending policy control beyond a simple session cap; include Stacks/sBTC support in the published SDK and/or MCP package with release notes and public documentation; publish a technical guide or walkthrough; document the intended Stacks x402 payment path, known dependencies, limitations, and any direct-broadcast fallback path; provide a final grant update with links to repository, release, documentation, demo, receipt ledger, transaction evidence, external validation evidence, and known limitations. External validation deliverables: at least two external developers, ecosystem teams, wallet teams, tooling teams, API providers, or agent builders test or review the integration; at least one external party reproduces the demo or confirms the integration flow using public documentation; validation must be documented through written feedback, GitHub issues, PRs, feedback threads, public posts, demo confirmations, Loom walkthroughs, or direct written feedback shareable with the Stacks Endowment.