Trust & security
Security
Standing rule: no publicly reachable admin surface without server-side auth. Sealed skill payloads are not in the public catalog. Confirmed unlocks are verified on-chain.
1. Payment security (x402)
- Live purchases use HTTP 402 challenges with explicit
maxAmountRequiredandpayTo. - Unlocks require a verifiable Base USDC transfer; the server checks chain state before releasing sealed files.
- Demo / fake unlocks are disabled in production unless an explicit operator env allows them (not enabled for buyers).
- Public ledger: /api/proof — confirmed purchases only (zeros are honest).
- Treasury address is published for transparency; never send funds to addresses outside the live challenge.
2. Sealed packs & catalog
- Public catalog.json exposes metadata and free evaluation links, not sealed implementations.
- Full packs unlock only after payment verification (or re-redeem with the same valid proof).
- Optional packaging metadata (container scans/signatures) is additive and only reported when tools produce it — see /trust/packaging/.
3. Machine surfaces
- /api/health — public health, no secrets.
- /api/shop, /api/catalog — discovery without payment bypass.
- A2A Agent Card · llms.txt · OpenAPI for agent clients.
- Rate limits and edge protections reduce automated abuse.
4. What we protect
- Server secrets (treasury keys, API tokens, KV credentials) stay in host environment — never in git.
- Ops/dashboard paths require authentication when enabled.
- Upload paths reject known-bad categories (scam patterns, illegal content policies).
5. What you must protect
- Your wallet seed phrases and private keys (we never ask for them).
- Transaction hashes used for re-download — treat them like receipts.
- Agent runtime secrets if a skill instructs you to store API keys in your environment.
6. Responsible disclosure
Found a vulnerability in payment verification, auth, sealed-pack delivery, or admin exposure?
- Report privately via the contact paths on /about/ or the operator listed in the repository security policy.
- Do not open a public GitHub issue for payment bypass, key material, or active exploitation details.
- Include: impact, steps to reproduce, affected URL/endpoint, and whether you have a proof-of-concept (describe; do not weaponize against production).
- We aim to acknowledge valid reports promptly and prioritize payment-path issues first.
Machine-readable pointer: /security.txt · /.well-known/security.txt
7. Verify us yourself
- Brand identity: /status.json
- Free sample before pay: agent-x402-first-buy outline
- Payment challenge: /api/pay?skill=agent-x402-first-buy
- On-chain proof: /api/proof
- BaseScan treasury token transfers (published address on status page)
8. Related policies
Privacy Policy · Terms of Service · Learn: Security and trust · Trust hub