Application-controlled x402 purchase

One supplier report. One bounded approval.

API Acre turns a legal or trading name into fresh, source-separated evidence from GLEIF, USAspending, SEC, and OFAC. An application can expose this call to an agent while retaining control of the merchant, purpose, exact amount, approval, idempotency, and receipt checks.

$0.1 USDC maximumBase mainnetx402 v2 exactPOST JSON
Review the live quoteInspect free sample JSONMachine-readable contract

Why this contract exists

The official OpenAI cookbook demonstrates a procurement agent requesting a paid supplier report through an application-defined x402_fetch tool. Its central boundary is sound: the model proposes a useful purchase, while application code owns approval and spending policy. API Acre supplies a real Base-mainnet merchant contract for that use case; it does not replace the buyer application's controls or payment provider.

Read the official OpenAI controlled-agentic-commerce cookbook.

Pin the purchase policy outside model control

{
  "resource_url": "https://apiacre.com/v1/research/organization-evidence",
  "method": "POST",
  "purpose": "supplier_due_diligence",
  "maximum_amount": "0.1",
  "currency": "USDC",
  "network": "eip155:8453",
  "human_approval_required": true,
  "one_use_capability": true
}

The live HTTP 402 challenge remains authoritative. Before requesting a payment proof, validate its recipient, amount, network, asset, expiry, resource, method, request body, approved purpose, and remaining budget.

Send one bounded supplier request

POST https://apiacre.com/v1/research/organization-evidence
content-type: application/json
Idempotency-Key: <application-owned unique key>

{
  "legal_name": "Apple Inc.",
  "country_code": "US",
  "sec_identifier": "AAPL"
}

An unpaid POST returns the x402 terms and executes no research. The paid retry returns a fresh structured result only after successful settlement.

Verify evidence before the agent summarizes it

  1. Require HTTP success and parse PAYMENT-RESPONSE as settlement evidence.
  2. Match the receipt to the application-owned amount, network, asset, and request.
  3. Match data.query.legalName to the approved supplier input.
  4. Inspect data.coverage and preserve unavailable-source warnings.
  5. Keep GLEIF, USAspending, SEC, and OFAC results separate: name similarity does not prove identity or cross-source linkage.
  6. Let the agent summarize evidence for human review; do not turn candidate matches into sanctions, compliance, credit, or procurement clearance.