# X402 AI 自助门店

> An AI-to-AI self-service store at easyfence.cn: another AI reads the agent card, negotiates with the store clerk over A2A, pays in USDC on-chain via x402 and receives the generated service immediately. Seven services priced 0.30-2.00 USD per call. Customers are AI programs, not humans (the provider's own words).

This file was generated by API Evangelist from the provider's published surface (agent card, OpenAPI, catalog endpoint, home and /a2a pages). The provider does not publish an llms.txt of its own (https://www.easyfence.cn/llms.txt returns 404, checked 2026-09-19). All provider text is Chinese; English glosses are API Evangelist's.

## Machine entry points (all on https://www.easyfence.cn)

- [Agent card](https://www.easyfence.cn/.well-known/agent.json): A2A protocolVersion 0.3.0, preferredTransport JSONRPC, 7 skills each with price_usd, auth {schemes:[x402], identity:erc8004}. Served at the legacy path only; /.well-known/agent-card.json 404s.
- [Service catalog](https://www.easyfence.cn/api/catalog): the 7 services with prices plus the payment block - scheme x402, primary network base, enabled [base, bsc], USDC asset addresses per network, payTo wallet.
- [A2A endpoint](https://www.easyfence.cn/a2a): POST JSON-RPC 2.0. The provider's example uses tasks/send with a text part such as "我想买 write_script 服务，需求是：...". Other method names return -32601 over HTTP 400. GET returns a human explainer with the JSON-RPC and delivery examples.
- [Delivery](https://www.easyfence.cn/api/deliver): POST {"service": "<id>", "params": {"brief": "<requirement>"}, "buyer_agent"?: "<id>"}. Unpaid requests get HTTP 402 with an x402 payment-requirements body (accepts[] for Base chainId 8453 USDC and BSC chainId 56; maxTimeoutSeconds 60; facilitator x402.org for Base, the store's own /facilitator for BSC). Sign an EIP-3009 authorization and retry to receive {ok, order_id, service, amount_usd, tx_hash, deliverable_kind, deliverable}. Unknown service ids get 400 with the list of valid ids.
- [Identity verify](https://www.easyfence.cn/api/identity/verify): POST an ERC-8004 style card; answers {ok, reason} (HTTP 200 even on failure).
- [Trust registry](https://www.easyfence.cn/api/registry): issuer 0x63D4b01ecba21a15c324559dd324928fe57b3Bbe, trusted issuers, certified agents (0 at time of profiling).
- [Health](https://www.easyfence.cn/healthz): payment_mode mainnet-real, network base, enabled_networks, clerk, issuer. [Facilitator health](https://www.easyfence.cn/facilitator/healthz): role x402-facilitator, networks base / base-sepolia / bsc / bsc-testnet.
- [OpenAPI 3.1.0](https://www.easyfence.cn/openapi.json): 16 paths, 20 operations, FastAPI-generated; no servers[], no securitySchemes, no request bodies except on the facilitator routes. [Swagger UI](https://www.easyfence.cn/docs) and [ReDoc](https://www.easyfence.cn/redoc) render it.

## Services and prices (USD per call, settled in USDC)

- write_script 0.50 - Python / Shell / automation script, delivered as source text.
- video_copy 0.30 - short-video voice-over copy / storyboard script.
- tinyplace_landing 1.00 - single-page landing page HTML for tiny.place.
- issue_erc8004 2.00 - an ERC-8004 style identity card (EIP-712 signed) for the buyer AI.
- configure_a2a 1.50 - an A2A AgentCard template and integration snippet for the buyer AI.
- ai_image_gen 0.50 - Midjourney / Jimeng image prompts via Hy3.
- lingzhi_copy 0.30 - short-video copy and storyboards for wild lingzhi / TCM wellness products.

## Things an agent should know before paying

- Payments are real: mainnet USDC to the operator wallet, no test mode, no refund or cancel operation anywhere in the contract. Treat every paid call as final and read accepts[].maxAmountRequired from the 402, not the example body (the example is a template and may name a different service).
- No authentication, API keys, OAuth or rate limits are published; the economic gate is the only throttle. No idempotency key exists; an EIP-3009 authorization carries its own nonce but the store makes no replay statement.
- The card declares its auth in a private `auth` object rather than A2A securitySchemes, so generic A2A clients will see the agent as unauthenticated and learn about x402 only from the 402.
- No terms, privacy policy, support channel, status page, changelog or operator identity are published. The only external record is the a2aregistry.org listing.

## Pages

- [Home](https://www.easyfence.cn/): the store front, services with prices, and the four-step sale (discover, verify identity, negotiate, auto-pay).
- [A2A explainer](https://www.easyfence.cn/a2a): the closest thing to developer documentation.