Buy with
HTTP 402

x402 · Agent commerce

AI agents can purchase our fixed-fee services programmatically — no sales call required.

x402 is the open protocol that revives HTTP status 402 “Payment Required”: a server answers a request with a payment challenge, the client settles on-chain, and retries with proof of payment. We support it for every fixed-fee SKU in our catalog.

This page is the complete contract — human-readable and machine-readable. If you are an agent, start at /.well-known/x402.json.

The flow

Three steps from discovery to a booked engagement. All endpoints are public and unauthenticated until payment.

x402 purchase flow
# 1. DISCOVER — who is this vendor and what do they sell?
GET https://proxpert.ae/.well-known/x402.json
GET https://proxpert.ae/api/services.json

# 2. CHECKOUT — pick a SKU, request its challenge
GET https://proxpert.ae/api/x402/checkout/seo-audit
# → HTTP 402 Payment Required
# → body: accepts[] with scheme, network, asset, amount, payTo

# 3. SETTLE — pay USDC on Base, retry with payment payload
POST https://proxpert.ae/api/x402/checkout/seo-audit
X-PAYMENT: <signed x402 payment payload>
# → HTTP 200 OK + booking confirmation

Endpoints

EndpointMethodPurpose
/.well-known/x402.jsonGETProtocol discovery: version, networks, assets, catalog location.
/api/services.jsonGETMachine-readable catalog: 7 SKUs, fixed prices in AED & USDC, deliverables.
/api/x402/checkout/{sku}.jsonGETStatic mirror of the HTTP 402 challenge for that SKU (see note on live wallets below).
/api/x402/checkout/{sku}POSTLive settlement endpoint. Send the signed payment payload in X-PAYMENT.
/llms.txtGETLLM-oriented summary of the studio, services and this protocol.

Catalog & SKUs

Seven fixed-fee entry products — one per service. Prices in AED with a binding USDC equivalent (USD peg 3.6725, rounded).

SKUProductAEDUSDCCheckout
seo-auditSEO Audit · 2 weeks28,0007,600challenge
paid-ads-auditPaid Media Audit · 10 days18,0004,900challenge
brand-strategy-sprintBrand Strategy Sprint · 2 weeks22,0006,000challenge
web-discoveryWeb & E-Commerce Discovery · 2 weeks25,0006,800challenge
ai-marketing-pilotAI Marketing Pilot · 4 weeks40,00010,900challenge
ai-workshopAI Workshop · half-day, ≤12 people12,0003,300challenge
solutions-discoveryCustom Software Discovery · 2–4 weeks25,0006,800challenge

Challenge format

Checkout challenges follow the x402 v1 response shape. Example for seo-audit:

402 response body
{
  "x402Version": 1,
  "error": "X-PAYMENT header is required to purchase this service",
  "accepts": [{
    "scheme": "exact",
    "network": "base",
    "maxAmountRequired": "7600000000",
    "resource": "https://proxpert.ae/api/x402/checkout/seo-audit",
    "description": "SEO Audit (2 weeks, fixed fee) — …",
    "mimeType": "application/json",
    "payTo": "0x…",
    "maxTimeoutSeconds": 86400,
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": { "name": "USD Coin", "version": "2" }
  }]
}

Settlement & fulfilment

  • Asset: USDC on Base (0x833589fC…A02913), scheme exact.
  • Live wallets: the static JSON mirrors publish a zero payTo on purpose. The live settlement wallet is issued with the engagement SOW — request it via POST on the checkout resource or by emailing hello@proxpert.ae with subject x402 <sku>.
  • Human in the loop: on settlement, a human project lead is assigned within 24 hours. Kickoff is scheduled with the buyer (or the buyer's human).
  • Refunds: if we cannot start within the window stated in the SKU, the payment is returned in full on the same rail.
  • Invoices: a VAT invoice (UAE) is issued for every settled SKU — to the buyer entity named in the booking confirmation.

For agent developers

  • Use any x402-compatible client (e.g. @coinbase/x402 fetch wrapper) pointed at our checkout resources.
  • Respect maxTimeoutSeconds (24h) — quotes are stable within that window.
  • Include a contact email in your payment metadata so we can reach the human behind the agent.
  • The full studio context is at /llms.txt; the long-form version at /llms-full.txt.

Security notes

  • Never send payments to a payTo address not confirmed inside a signed SOW or the live POST response.
  • The static .json mirrors are discovery documents, not payment invitations.
  • Verify TLS and the exact domain proxpert.ae before settling.

Humans still
welcome.

Prefer email to USDC? Same services, same prices — write us and we'll handle the rest.