Conversation
* docs: add llms.txt intro page for AI agents (#256) Add a GitBook-friendly page introducing PolyPay's llms.txt support so non-technical readers can discover the feature and link AI agents to the live playbook. - New page docs/llms-txt-for-agents.md covering what llms.txt is, the live endpoint, the five integration flows it documents, two ways to wire an agent up, and compatibility notes. - Add the page to docs/SUMMARY.md between x402 and Architecture. - Fix stale api.polypay.xyz references in docs/x402-deposits.md to the real api.polypay.pro host. * feat(x402): add Coinbase CDP bazaar deposit route for agentic.market listing (#260) Adds a second x402 deposit endpoint /x402/bazaar/deposit/:multisig that routes through Coinbase CDP facilitator instead of PayAI, so the resource gets indexed in CDP discovery and surfaces on agentic.market. The default /x402/deposit/:multisig path keeps using PayAI (better rate limits, simpler auth) — no UI change. CDP path activates implicitly when CDP_API_KEY_ID is set; otherwise it returns a clear config error. CDP requires Ed25519 JWT signed per-request (2-min TTL), so the service now lazy-imports @coinbase/x402 createAuthHeader to produce the Authorization header. Payment requirements for the CDP path also embed a declareDiscoveryExtension-shaped extensions.bazaar block (strict JSON Schema), without which CDP would settle but not index. Includes scripts/bazaar-bootstrap.ts to produce the first real settlement that triggers CDP indexing — bootstrap must run against a deployed backend (the resource URL ends up in the catalog). Refs #259 --------- Co-authored-by: BoHsuu <[email protected]>
CDP indexer stopped picking up v1 (outputSchema) entries — verified by 3
successful v1 settlements on Base mainnet + Base Sepolia that never
appeared in /discovery/merchant after 15+ minutes. All entries CDP
indexed today are x402Version: 2 with extensions.bazaar at the top
level of PaymentRequired. The v1 ranking in CDP appears deprecated in
practice.
Types and wire format taken directly from
@x402/core/src/types/payments.ts so the shape matches what CDP's
facilitator expects:
- paymentRequirements.amount (was maxAmountRequired in v1)
- paymentRequirements.network CAIP-2 "eip155:8453"
- paymentPayload.accepted (chosen requirement, v2-only)
- PaymentRequired.resource ResourceInfo object {url, ...}
- PaymentRequired.extensions.bazaar top-level, not on accepts[]
PayAI path is untouched and stays on v1, which is what
facilitator.payai.network currently indexes (PolyPay listing is live
there). The same EIP-3009 signature works across versions, so the
bootstrap script and the UI keep sending v1 X-PAYMENT; only the CDP
forwarding step translates to v2.
Refs #259
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.