Screening reports / 企业筛查报告: Standard screening-standard-v1 costs 0.29 USDC for ten fixed Jinghai-first check dimensions, with JSON and Chinese/English HTML reports. Only if administrative-license check v3_license_list has a connection/call failure or is already circuit-open, one QCC get_administrative_license fallback is made (3 points, up to 100 records, no paging or retry). Enhanced screening-enhanced-v1 costs 0.59 USDC for the same ten dimensions plus one QCC qualifications lookup (up to 30 records), so at most two QCC calls total. The license fallback preserves both source outcomes but does not claim complete license records; no other check falls back and this is not fallback across all 64 tools. Other check failures or failure of both providers prevent settlement. QCC qcc-qualifications-v1 costs 0.03 USDC and returns canonical JSON only, up to 30 records, without report analysis. Screening reports also support get_china_company_report through the MCP facade over the same HTTP x402 checkout; QCC-only qualifications remain HTTP-only. Free MCP options and recovery tools are available. On 2026-10-15, one owner-funded 0.29 USDC Standard MCP test via the public Python example returned all ten contracted dimensions in 15.78 seconds, reconciled exactly one settlement, exercised the QCC administrative-license fallback, and recovered identical JSON plus both HTML languages without new provider calls or payment. This was not complete due diligence; the decision remained insufficient_evidence and this was not customer traction. The current Enhanced and Resilient contracts have no funded acceptance. No funded acceptance covers the complete 64-tool catalog; the separately documented HTTP v3_company_detail test does not establish acceptance of that full catalog. Delivery depends on provider balance and runtime availability; there is no manual daily or total commercial quota, but single-order limits and delivery conditions still apply. See the product overview, conditions and current acceptance status and live product catalog before purchase.
标准版0.29 USDC：10个固定维度，优先查询鲸海；仅当行政许可工具（v3_license_list）连接/调用失败或已熔断时，才调用一次企查查 get_administrative_license（3积分、最多100条，不翻页、不重试）。增强版0.59 USDC：同样10个维度，另始终查询一次企查查资质（最多30条），企查查最多调用两次。许可回退保留两个来源结果，但不声称记录完整；其他检查不回退，也不是全部64个工具均有兜底。其他检查失败或两家服务商均失败时不结算。单独企查查资质0.03 USDC：仅规范JSON、最多30条，不含报告分析。整份筛查报告也可用 get_china_company_report，经 MCP 转接同一 HTTP x402 结算链路；企查查资质单项仍仅支持 HTTP。另有免费套餐查询及原单恢复工具。2026-10-15，一次由所有者出资的0.29 USDC标准版MCP测试通过公开Python示例完成，15.78秒返回全部十项合同范围内容，核对为恰好一次结算，触发企查查行政许可回退，并恢复出相同JSON及中英文HTML，未新增服务商调用或付款。该报告不是完整尽调，结论仍为 `insufficient_evidence`；这是内部测试，不代表客户需求。当前增强版、韧性版合约尚无实付验收；尚无实付验收覆盖完整的64工具目录，另有记录的一次 v3_company_detail HTTP 测试不代表完整目录通过验收。交付依赖服务商余额和运行可用性；请查看产品说明、条件及当前验收状态和实时目录。
Current V3 catalog: 64 individual data tools at 0.011 USDC per call; MCP tools/list has 71 definitions, including 3 report workflow tools. See the V3 call guide and live catalog. The Basic/Full prices below cover retained legacy packages only.
Home · Read a fictional supplier-check example / 先看懂报告示例 · Matching sample JSON · Live API schema
New to CN Evidence? See what the output can and cannot tell you before configuring a wallet. It is a fictional worked explanation, not a live report or a supplier-safety verdict.
Paid data, not a free MCP lookup. Connecting MCP and listing tools are not purchases. Legacy Basic costs 0.032 USDC; legacy Full costs 0.093 USDC. Check the live quote before signing. Payment is x402 v2, exact, USDC on Base mainnet (eip155:8453), not Base Sepolia.
连接成功不等于能付款。 查询需要买方的钱包、Base 主网 USDC 余额和消费授权。钱包由买方保管，不要向我们、聊天窗口或公共配置提交私钥。当前没有预充值 API Key 方案；原生 MPP 暂停。
| Your client | What is needed |
|---|---|
| AgentCash-enabled agent | Its wallet setup, sufficient Base USDC and owner spending approval. Use our HTTP routes. Documentation-level candidate; no funded end-to-end compatibility certification is claimed. |
| Custom x402 HTTP client | x402 v2 exact/EVM signer and guarded signature/retry flow. Validate network, asset, recipient and amount against the approved operation before signing. |
| x402-aware MCP client | Must interpret the tool's Payment Required result and send the SDK's MCP payment metadata. HTTP payment headers are not a substitute for MCP metadata. |
| Plain remote MCP client | Can discover tools; requires an x402 payment client or local HTTP-to-MCP payment bridge to buy data. Do not assume the host supplies a wallet. |
Read the sample and schema first. The following request only gets a quote. It has no payment signature, is marked as an internal/developer test and does not buy a report:
curl -i -A "CN-Evidence-Monitor/docs-check" -H "X-CN-Traffic: internal_test" https://api.cnevidence.com/x402/cn/supplier/evidence/basic
HTTP 402 means payment is required, not server downtime. For native MCP, HTTP 200 may carry result.isError=true and structuredContent.error="Payment Required"; that is not company data or a completed purchase. Do not repeatedly retry without a valid payment client.
Use POST to https://mcp.cnevidence.com/mcp with Content-Type: application/json and Accept: application/json, text/event-stream. Prefer a current Streamable HTTP MCP SDK for the normal initialize/notification lifecycle. This stateless service also accepts the following direct tools/list diagnostic; it lists tool definitions only, not company data.
Download mcp-tools-list.json into your current folder. On Windows PowerShell use curl.exe explicitly:
curl.exe -i "https://mcp.cnevidence.com/mcp" -A "CN-Evidence-Monitor/docs-check" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -H "X-CN-Traffic: internal_test" --data-binary "@mcp-tools-list.json"
On macOS/Linux replace curl.exe with curl. Expected: HTTP 200 with 71 tool definitions (64 individual data tools, the three legacy tools, a free schema helper and 3 report workflow tools). No wallet or company identity is needed for discovery. The internal-test header is for diagnostics only; omit it for real customer queries. Use the V3 guide for new-tool identity rules; the company/USCC examples below describe legacy Basic/Full only.
| Result | Meaning and action |
|---|---|
| 406 / Client must accept application/json | The current JSON-response service rejects Accept: */*, text/html, or text/event-stream alone on POST. Send the explicit Accept header above. A browser address-bar visit is not an MCP handshake. Do not repeatedly retry unchanged requests. |
| 400 / JSON-RPC error | Check valid JSON, method, protocol negotiation and request shape; read the returned error. Not automatically a server outage. |
| 404 / 405 | Check endpoint and method. MCP is /mcp; the HTTP Full report is POST, not GET. The protocols are not interchangeable. |
| 422 / invalid_tool_input | For legacy Basic/Full, check company/USCC and nesting: Basic uses query, Full uses request. For V3, use its own argument schema and nesting; legacy USCC input is not interchangeable. Correct identity before purchase. |
| HTTP 402 or MCP Payment Required | Connection can be working; a configured payment client and explicit authorization are still required. This is not a delivered report. |
| 5xx / timeout | Record time, request ID if available and sanitized error. If payment may already have been submitted, reconcile first rather than blindly buying again. Never share signatures or private keys in diagnostics. |
上述错误数字是请求结果，不是客户数量。连接探测、页面抓取和付款查询必须分开统计。
New: free input preflight, not a lookup. Before purchasing, POST a JSON object with company or uscc to https://api.cnevidence.com/free/cn/identity/preflight. It checks local format and prepares Basic/Full HTTP and MCP request shapes. It makes no upstream call, needs no wallet, and cannot verify company existence, USCC checksum, name/code agreement or absence of risk.
Alternatively call the existing free MCP tool resolve_china_company with company and/or uscc. Despite its legacy name, it does not resolve entities. An English-only brand/name prompts you to obtain a Chinese legal name or USCC; it is never translated into an assumed company.
Download the fictional diagnostic input and run:
curl.exe "https://api.cnevidence.com/free/cn/identity/preflight" -A "CN-Evidence-Monitor/docs-check" -H "Content-Type: application/json" -H "X-CN-Traffic: internal_test" --data-binary "@preflight-input.json"
Expected for this English-only example: input_ready: false and guidance to obtain the legal identifier. A correctly formatted Chinese name/code can return input_ready: true, but always identity_verified: false. This is not permission to pay. Confirm the entity separately; do not auto-purchase just because preflight passes. Omit the internal-test header for real user preparation; do not upload identity documents or unrelated personal information.
company: exact Chinese registered legal name, or uscc: 18-character Unified Social Credit Code.Basic HTTP: GET /x402/cn/supplier/evidence/basic?uscc=YOUR_CONFIRMED_USCC
Full HTTP: POST /x402/cn/supplier/evidence
JSON body: {"uscc":"YOUR_CONFIRMED_USCC"}
MCP endpoint: https://mcp.cnevidence.com/mcp
Basic tools/call params:
{"name":"get_china_supplier_evidence_basic","arguments":{"query":{"company":"CONFIRMED_CHINESE_LEGAL_NAME"}}}
Full tools/call params:
{"name":"get_china_supplier_evidence_full","arguments":{"request":{"company":"CONFIRMED_CHINESE_LEGAL_NAME"}}}
Looking for the 0.29 USDC Standard report? Use the separate Standard client and recovery instructions. It covers ten Jinghai-first check dimensions, with only the conditional QCC administrative-license fallback described above; other checks do not fall back. The legacy/detail client below does not buy Standard. The new Standard helper has offline and unsigned checks, not a fresh funded-client acceptance.
Download and review purchase-client.mjs and recovery-client.mjs. The example supports V3 company detail by exact Chinese name and the two legacy packages. It defaults to a free quote, with local format checking only (legacy uses the free preflight). A quote does not check upstream availability or company existence. Explicit --pay permits one signed attempt, pins the chain, asset, recipient and price, and saves a private recovery credential before signing. On an uncertain response it attempts free recovery once, never another purchase. It is an HTTP example, not a plug-in that makes a plain MCP host pay.
npm install @x402/core@2.25.0 @x402/evm@2.25.0 viem@2.56.3 # V3 company detail: free preview, no wallet or installed SDK required: node purchase-client.mjs --tool v3_company_detail --company "CONFIRMED_CHINESE_LEGAL_NAME" # Only after purchase approval and secure local wallet configuration: node purchase-client.mjs --tool v3_company_detail --company "CONFIRMED_CHINESE_LEGAL_NAME" --pay --max-usdc 0.011 --state NEW_PRIVATE_RECEIPT.json --out NEW_REPORT.json # Alternative legacy Basic package (separate purchase, not a prerequisite): node purchase-client.mjs --tier basic --company "CONFIRMED_CHINESE_LEGAL_NAME" # Only after purchase approval and secure local wallet configuration: node purchase-client.mjs --tier basic --company "CONFIRMED_CHINESE_LEGAL_NAME" --pay --max-usdc 0.032 --state NEW_PRIVATE_RECEIPT.json --out NEW_REPORT.json # Full uses --tier full and --max-usdc 0.093. # After an interruption, keep the SAME receipt and do not start another purchase: node recovery-client.mjs status NEW_PRIVATE_RECEIPT.json node recovery-client.mjs recover NEW_PRIVATE_RECEIPT.json --out RECOVERED_REPORT.json
Replace the placeholder with the exact Chinese legal name before previewing. V3 example mode accepts --company only, not --uscc or company IDs; other V3 tools require a separately reviewed client following their schemas. A returned V3 report must match the requested tool and company name, indicate successful business processing, and contain agreeing structured/text results before this purchase client saves it. Name matching only normalizes surrounding whitespace and full-width parentheses, not brands or fuzzy names.
Provide CN_EVIDENCE_PRIVATE_KEY only through a trusted local secret manager or protected environment, never a command-line argument, chat, source repository or our server. Keep receipt/report files in a private folder; Windows users must restrict its ACL. The per-attempt cap is not a cumulative wallet budget: creating new receipt files can authorize more purchases. Existing files are never overwritten. Client tests cover simulated delivery, identity mismatch, timeout/recovery and live unpaid quotes; this exact packaged client has not had a separate funded acceptance run. Earlier service acceptance is described below.
Only run after the owner approves the purchase and confirms the entity. These commands can spend wallet funds. Configure and review the buyer tool's controls first; the examples themselves do not enforce a cumulative budget. Do not use an unrestricted auto-paying client if you require an enforced budget.
npx agentcash@latest fetch "https://api.cnevidence.com/x402/cn/supplier/evidence/basic?uscc=YOUR_CONFIRMED_USCC"
npx agentcash@latest fetch "https://api.cnevidence.com/x402/cn/supplier/evidence" -m POST -b '{"uscc":"YOUR_CONFIRMED_USCC"}'
For production pin a reviewed client version. For a custom SDK enforce per-call caps (Basic 0.032, Full 0.093 USDC), a separate total budget, approved destination/asset/network, and no blind retry after an uncertain payment. Save receipts securely and reconcile before purchasing again. Never accept a changed quote automatically.
The free JSON is hand-authored fictional schema guidance, not a live API response. It performs no query. Each selected list is page 1, at most 10 records; no automatic history or pagination. “No records” is not proof of no risk. Nine modules are not nine fields, and this is not a complete due-diligence or supplier-safety judgment.
本示例完全虚构，不能作为真实企业证据。不要把示例下载、工具发现或内部测试算成客户成交。
V3 acceptance, 2026-10-10: one owner-funded HTTP v3_company_detail purchase at 0.011 USDC passed payment, settlement, report delivery and free recovery checks. Recovery returned the same report without another upstream query or payment. This does not certify all 64 tools, V3 MCP payment, AgentCash or every client. Delivery depends on provider balance and runtime availability; there is no manual daily or total commercial quota, but per-order limits and delivery conditions remain. See the V3 failure and recovery guide.
On 2026-09-22 we completed owner-funded internal acceptance: HTTP Basic (0.032 USDC), MCP Full (0.093 USDC), and MCP Basic with its original response body discarded and then recovered twice (0.032 USDC, no extra payment or upstream query on recovery). Chain transfers, client reports and server records were checked. These are internal tests, not customers or certification of AgentCash or every third-party client.
Configure before the purchase. Generate 32 cryptographically random bytes and encode them as 64 lowercase hexadecimal characters. Save this unique secret securely before signing. Send it as X-CN-Recovery-Token on the actual paid HTTP or MCP POST request. Do not reuse it for a different purchase. The server stores its hash, not the token. A public transaction hash, payment signature, nonce or order ID is not a recovery credential.
If the original connection or response is lost, send the following JSON by HTTPS POST to https://api.cnevidence.com/free/cn/payment/recover with Content-Type: application/json. Do not attach a payment signature. The same recovery endpoint supports both HTTP and MCP purchases.
{"recovery_token":"YOUR_SAVED_64_HEX_SECRET","include_report":true}
This operation never charges or calls the upstream provider. include_report:false requests status only. HTTP 200 with state: settled and a report returns the original report when requested. For new opted-in V3 attempts, HTTP 200 can instead carry state: failed_before_settlement, settlement_attempted:false and no report; it means this service did not attempt settlement, not that upstream usage was free. HTTP 202 means processing or settlement remains uncertain and requires reconciliation; 404 means no matching order; 410 means the status/report recovery window expired. Read the response body, not just the HTTP code. Do not interpret an unknown order or timeout as permission to pay again.
New opted-in V3 requests bind the saved recovery token before the upstream query, so status can be looked up even if no report was prepared. Recorded settlement state takes precedence over an earlier failure marker. Repeated upstream failures temporarily pause only the affected tool. The service does not automatically retry the query, repay, or substitute a non-equivalent legacy tool. Old requests are not backfilled; loss of the whole local database remains outside this protection.
The report is retrievable for 24 hours from preparation; expired bodies are removed on subsequent recovery/storage access. This is not permanent storage or a refund guarantee. Requests without the header, purchases before this feature, and lost tokens do not get automatic recovery. Clients must implement the header and recovery call; adding a plain MCP URL does not do this automatically. Recovery credentials belong only in the header or HTTPS JSON body, never a URL, public log, or support email.
If you have the original recovery secret and an existing Base transaction hash from your payment receipt, add transaction_hash to the recovery JSON. This does not send a transaction. The server checks finalized Base USDC events, matching the original payer and authorization nonce, the configured recipient, and exact amount. Only a matching confirmed payment releases the stored report. A transfer alone, a public hash alone, or a wallet balance change is insufficient.
{"recovery_token":"YOUR_SAVED_64_HEX_SECRET","include_report":false,"transaction_hash":"YOUR_EXISTING_0x_TRANSACTION_HASH"}
Checks are limited to once per minute per uncertain order. Pending, not-finalized, mismatched, rate-limited or unavailable RPC results do not mean unpaid: do not buy again automatically. A missing transaction hash, ambiguous/multiple USDC events, lost/expired report, or changed recipient configuration may still require manual support. This relies on a public RPC with no availability guarantee, is not an automatic refund, and does not guarantee recovery from every crash. Finalized-chain matching was tested against an existing real internal transaction and an isolated simulated uncertain order; we did not manufacture a new live settlement failure.
Storage failure handling (new opted-in orders): Before settlement, the service stores an integrity hash and a second private local report copy. If the primary record is missing, corrupted or modified, recovery can restore the matching copy without another purchase or upstream query. Both copies use the same 24-hour window. This is not off-site disaster recovery and does not cover complete disk/database loss, lost credentials or requests made before this feature.
If a confirmed-paid report cannot be restored before expiry, the response is HTTP503 with error: stored_report_unavailable and a deduplicated refund.status: review_required. This is a review record, not a completed or promised refund. A separate bounded worker now processes eligible confirmed server-side delivery/storage failures: full original amount, original on-chain payer only, at most 1 USDC per UTC day. It rechecks restored reports and finalized chain evidence, retains uncertain reservations, and never blindly resends. Wrong identity, normal expiry, lost credentials and already delivered reports are not automatically eligible. HTTP409 means execution reconciliation is required. Only refunded_confirmed means the refund was independently finalized on-chain; the recovery endpoint itself never transfers money.
One owner-authorized 0.032 USDC internal refund was finalized and reconciled on 2026-09-22. This is not customer activity or a blanket refund guarantee. The signer runs on a separate operator computer every five minutes while that computer is online and its user is logged in; it is not an always-on cloud signer. Insufficient funds, unavailable RPC/relay, daily cap or ambiguous transactions require follow-up. Health status expires if the worker stops.
As of 2026-09-24, encrypted audit-ledger and monitoring backups run hourly on the server and are stored privately off-server with a 30-day retention policy. A timer-triggered backup was downloaded, decrypted and integrity-checked successfully. This backup excludes report bodies, recovery credentials, wallet keys and live payment runtime state: it does not extend the 24-hour report-recovery window or provide full-server/payment-state disaster recovery. Decryption uses an operator-held age recovery key, not Windows DPAPI. The separate refund signer still depends on the operator computer as described above; cloud backups do not make it always-on. Never restore a stale ledger into an active signer without chain reconciliation.
Download and inspect recovery-client.mjs. No dependencies, private keys, signing, purchases or automatic retries. It can generate a recovery file, check MCP connectivity, query status, and save a recovered report. Use a private folder outside Git, cloud sync and shared storage; on Windows ensure its access permissions are restricted to your user. The helper never prints the token or report. It refuses to overwrite existing output files.
node recovery-client.mjs init private-recovery.json node recovery-client.mjs diagnose node recovery-client.mjs status private-recovery.json node recovery-client.mjs recover private-recovery.json --out recovered-report.json # For an uncertain order, supply an existing transaction hash (not a new payment): node recovery-client.mjs status private-recovery.json --txhash YOUR_EXISTING_0x_TRANSACTION_HASH
Important: init only creates a private file containing recovery_token and headers. Your separately configured payment client must read and send that X-CN-Recovery-Token header on the original paid request. This helper does not turn a plain MCP client into a paying client and cannot add recovery retroactively. Generate a unique file for each purchase. A diagnostic success proves tool discovery, not payment compatibility or a customer sale.
Available from 2026-10-11: combine already settled CN Evidence purchases into a rules-based, unreviewed company-screening report. This is an additional delivery format, not a new lookup or payment product. The operation makes no provider call and no additional charge; original evidence purchases retain their published prices. It does not automatically buy missing evidence or call QCC.
X-CN-Recovery-Token as described above. New purchases bind the original arguments, price and contract before settlement. Historical orders without this binding are not backfilled.https://api.cnevidence.com/free/cn/reports/compose. Do not send a payment signature. Never place tokens in a URL, screenshot, public log or support email.{"recovery_tokens":["SAVED_SECRET_FOR_REGISTRATION_ORDER","SAVED_SECRET_FOR_ANOTHER_ORDER"],"format":"json"}
Use format: "zh-CN" or format: "en" to receive a private HTML report; use "json" for structured analysis plus a separate verified-entitlement envelope. Download and keep the result privately. HTML is suitable for browser printing, but this endpoint does not generate PDF files. The analysis engine itself does not verify payments; the authenticated delivery layer separately verifies the selected source-order settlements.
Availability ends at the earliest selected order's 24-hour expiry. Repeated composition of the same selected snapshots returns the same stored analysis without another upstream query. Wrong tokens, inconsistent identities, different payers, missing bindings, uncertain settlements and refunded orders do not release an analysis. On HTTP404/409/422/503 inspect the error and existing order status; do not automatically buy again. A temporary delivery-capacity gate may also reject requests without charging.
The report identifies missing evidence and source limitations. A first page, provider count or empty response is not a complete investigation or a safety finding. Human review is required. This /compose endpoint never dispatches QCC. A separate, explicitly requested qualifications supplement is described below.
Acceptance scope, 2026-10-11: one owner-funded internal HTTP registration purchase at 0.011 USDC passed chain settlement, private recovery, paid-source analysis and JSON/Chinese/English delivery. Repeated delivery returned identical reports without another purchase or upstream call. The same order also completed the optional qualifications supplement below. This is one internal sample, not customer activity, full diligence coverage, or certification of all tools and clients. Isolated fixtures additionally cover denied access before settlement, refund blocking and audit-backup exclusion. Current requirements: analysis delivery metadata.
A bounded, gift-funded pilot is connected at POST https://api.cnevidence.com/free/cn/reports/supplement. It accepts the same recovery_tokens array and optional format (json, zh-CN, or en). It is not a new payment product: no additional customer charge, no payment signature. Never put recovery tokens in URLs or public logs.
First check current supplement availability. Only one accepted QCC qualifications lookup can be attempted per eligible registration-order anchor, with no automatic retry or pagination. Valid Jinghai evidence, including valid empty results, is retained; an enabled Jinghai check that has not been purchased is not silently bypassed. Identity conflicts stop supplementation. Source providers and any truncation are separately reported, not treated as independent corroboration.
HTTP 202 means queued, not queried or delivered. Repeat the identical POST after 10 seconds to collect. HTTP 200 includes the report and collection status; inspect collection and provider evidence, because a hold, unknown outcome or missing check is not a successful supplement or a finding of no risk. JSON has a collection field; HTML displays collection status. Changing source combinations does not create another supplement entitlement. Source-order expiry and refund restrictions still apply.
Admission requires a gift/purchased-balance observation no older than 15 minutes, a verified one-point unit price, an account-wide 20-point UTC-day ceiling and a one-point report ceiling. Historical reservations count toward the account limit. Purchased credits are not authorized. Availability can expire before dispatch; in that case no business call is made. This is not 24/7 QCC availability, and gift credits are not long-term zero cost. If unavailable, use /free/cn/reports/compose for the already purchased Jinghai report without QCC; do not purchase again just to retry this pilot.
Funded pilot acceptance, 2026-10-11: the same 0.011-USDC internal registration order received one QCC qualifications supplement. Provider account evidence confirmed one gift point consumed at each provider, with no recharge or purchased QCC credits. The supplement returned 30 records against a provider-claimed total of 90, with legal-name-only matching and incomplete coverage explicitly retained. JSON and bilingual HTML repeated identically, and the quota journals showed no second dispatch. Gateway ledger access and worker payment-ledger permissions were corrected during this acceptance; these controls were verified in the actual service environment.
中文：这是单项资质补查试点，不是企查查全部接口上线。优先保留鲸海证据；缺项和错误保持可见。有效额度窗口内才排队调用，过期停止补查；鲸海已有订单的报告合成不受影响。恢复凭证只放 HTTPS 请求正文。2026-10-11 已完成一次内部真实付款、鲸海查询、企查查资质补查及中英文报告交付；两家各消耗 1 个赠送积分，重复领取未产生第二次调用。资质仅返回 30 条，供应商声称共 90 条，报告保持“证据不足”，不冒充全量尽调或无风险证明。
Official x402 bridge and spending-policy guide · AgentCash documentation. Reference examples may use test networks; this service uses Base mainnet. Our internal custom-SDK acceptance does not certify those other clients.