x402 · HTTP 402 · USDC on Base

Aesthetic-medicine data, paid per call.

A pay-per-call data API for AI agents and developers. Each request is paid in USDC on Base through the x402 protocol. No signup. No API key.

Explore the endpoints OpenAPI spec

Base URL: api.aestheticdata.io
Payment: USDC on Base
Protocol: x402 (HTTP 402)
Auth: None. Payment is the credential

terminal

$ curl -i https://api.aestheticdata.io/x402/brands

HTTP/2 402
content-type: application/json
payment-required: eyJ4NDAyVmVyc2lvbiI6Mi…

# body is x402 v1 (network "base"); the v2 header uses eip155:8453
{
  "x402Version": 1,
  "error": "Payment required: …",
  "accepts": [{
    "scheme": "exact",
    "network": "base",
    "maxAmountRequired": "1000",
    …
  }]
}
# 1000 = 0.001 USDC (6 decimals)

Endpoints

Two datasets, priced per request

Both endpoints live under https://api.aestheticdata.io and return JSON. Prices are fixed and quoted in the 402 response before you pay.

GET/x402/brands

0.001 USDC / call

Aesthetic brand catalog

Partially verified

85 core brands covering dermal fillers, botulinum toxins and threads, returned in a single call.

Records: 85 core brands
Coverage: Dermal fillers
Botulinum toxins
Threads
Verification: Partially verified
Price: 0.001 USDC per call
Free sample: /sample/brands

Request URLhttps://api.aestheticdata.io/x402/brands

GET/x402/regulatory/eu/devices

0.002 USDC / page

EU aesthetic device registry

Data as of 2026-09-29

The aesthetic subset of public EUDAMED UDI-DI data: 14,266 records across 13 EMDN categories.

Records: 14,266
EMDN categories: 13

Fillers & kits
Breast and facial implants
Threads
Liposuction
Annex XVI aesthetic devices
Pagination: 100 records per page, 143 pages
Query: ?page=1 … ?page=143
Price: 0.002 USDC per page
Free sample: /sample/eu_devices
Data as of: 2026-09-29

Request URLhttps://api.aestheticdata.io/x402/regulatory/eu/devices

How it works

Request, pay, retry

Standard x402 over plain HTTP. There's no account to create and no key to rotate: the payment itself authorizes the request.

Request
Call an endpoint without payment. The API answers 402 Payment Required with the payment terms: price, asset and network.
Sign
Your x402 client signs a USDC payment authorization on Base for the quoted amount.
Retry
Send the same request again with the signed payment in a header. You receive the data.

x402 flow

# 1. Unpaid request: the server replies 402 with payment terms
$ curl -i https://api.aestheticdata.io/x402/brands

HTTP/2 402
content-type: application/json
payment-required: eyJ4NDAyVmVyc2lvbiI6Mi…
# ↑ x402 v2 terms (base64). The JSON body carries the v1 terms:

{
  "x402Version": 1,
  "error": "Payment required: send PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (x402 v1)",
  "accepts": [{
    "scheme": "exact",
    "network": "base",
    "maxAmountRequired": "1000",  # 0.001 USDC
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    …
  }]
}

# 2. Sign the payment with your x402 client, then retry
$ curl https://api.aestheticdata.io/x402/brands \
    -H "PAYMENT-SIGNATURE: <base64 payment payload>"

HTTP/2 200
# 3. JSON data in the response body

x402 client libraries can do steps 2 and 3 for you: they wrap your HTTP client, pay the 402 and retry automatically. x402 v1 clients send X-PAYMENT instead of PAYMENT-SIGNATURE; send one header, not both.

Discovery