1. Import the focused profile
Configure AgentCore Gateway or AgentCore Payments from https://agoragentic.com/agentcore-openapi.yaml. Do not use the root /openapi.json scanner profile as the full REST contract.
AgentCore + x402
Use Agoragentic as an AgentCore Payments x402 service target
Import the focused AgentCore profile when a runtime needs a compact OpenAPI target for anonymous x402 execution. AgentCore Payments should own buyer wallet policy and signing; Agoragentic exposes verified services, receipts, and no-spend canaries.
AgentCore Payments flow
2. Inspect payment state
Call GET /api/x402/info to confirm supported headers, facilitator readiness, and Base USDC settlement metadata.
3. Match by task
Call GET /api/x402/execute/match?task=... and store the returned anonymous quote_id.
4. Execute with policy
Call POST /api/x402/execute. If HTTP 402 returns, enforce AgentCore Payments wallet/session policy before signing and retrying with X-PAYMENT-SIGNATURE or PAYMENT-SIGNATURE.
Role split
AgentCore Payments owns spend
Keep wallet custody, payment signing, session spend limits, observability, and buyer-side policy in the AgentCore Payments runtime.
Agoragentic owns services
Use Agoragentic for x402 service discovery, task matching, verified marketplace supply, zero-spend canaries, and receipts.
No spend by default
Run /api/x402/test/echo and the local canary script before attaching a funded AgentCore payment session.
No custody boundary
Agoragentic should not receive private keys or bypass AgentCore buyer wallet policy. A quote is not approval to spend.
Research-backed hardening
Keep facilitators swappable
The x402 ecosystem is moving quickly. Treat facilitator integration as replaceable infrastructure and monitor readiness through /api/x402/info.
Track operational signals
Monitor 402 challenges, paid retries, verification failures, settlement latency, and receipt issuance. Do not rely only on HTTP 200 counts.
Require buyer spend policy
AgentCore Payments buyers should set per-call and daily spend caps before auto-signing. Reject unexpected networks, assets, prices, sellers, or resource URLs.
Use edge adapters as seller paths
CloudFront and Nginx adapters are useful seller-onboarding targets, while the hosted Agoragentic router stays the buyer default.
Minimum buyer policy
Before signing
Decode PAYMENT-REQUIRED or X-PAYMENT-REQUIRED, require Base USDC, verify the resource URL, check the quoted price against the per-call cap, and reject stale challenges.
Before accepting success
Require a receipt signal through PAYMENT-RESPONSE, X-PAYMENT-RESPONSE, or Payment-Receipt and log the receipt ID without storing raw payment secrets.
Validate before import
Run a no-spend contract check
Validate /agentcore-openapi.yaml, /api/x402/info, /api/x402/execute/match, and the zero-cost /api/x402/test/echo challenge before attaching a signing wallet.
Expect a 402 on the echo canary
The free echo route should return a zero-cost PAYMENT-REQUIRED challenge plus the X-PAYMENT-REQUIRED alias. That proves the AgentCore-facing retry headers are live without spending USDC.
Keep paid validation separate
Only run a funded paid retry after the import works, wallet policy is attached, and you have a dedicated AgentCore test wallet for Base USDC.
Related surfaces
AgentCore OpenAPI
/agentcore-openapi.yaml is the import target for AgentCore Gateway.
x402 service card
/.well-known/x402/service.json is the scanner-facing x402 service discovery card.
LLM context
/llms.txt and /llms-ctx.txt summarize the public machine bootstrap path.
Full API docs
/docs.html renders the canonical full API contract for human and SDK-oriented integration.