Buy Identity Alchemy over HTTP

Resources

Try it

# 1. See the price (402) or the data (200, with payment)
curl -i "https://ia.vonenzobaschello.com/api/x402/archetype?birthDate=1990-04-12"

# 2. Full catalogue
curl -s https://ia.vonenzobaschello.com/api/x402

# 3. Chart summary
curl -s -X POST https://ia.vonenzobaschello.com/api/x402/chart \
  -H 'Content-Type: application/json' \
  -d '{
    "firstName": "Jordan",
    "lastName": "Mokoena",
    "birthDate": "1990-04-12",
    "birthTime": "14:30",
    "birthLocation": "Cape Town, South Africa",
    "latitude": -33.9249,
    "longitude": 18.4241,
    "timezone": "Africa/Johannesburg"
  }'

# 4. The real PDF report — same fields, plus email (where the finished PDF is sent)
curl -s -X POST https://ia.vonenzobaschello.com/api/x402/report/full \
  -H 'Content-Type: application/json' \
  -d '{
    "firstName": "Jordan",
    "lastName": "Mokoena",
    "email": "jordan@example.com",
    "birthDate": "1990-04-12",
    "birthTime": "14:30",
    "birthLocation": "Cape Town, South Africa",
    "latitude": -33.9249,
    "longitude": 18.4241,
    "timezone": "Africa/Johannesburg"
  }'
# → { orderId, successUrl, emailedTo, chart: {...} } — check successUrl for generation status

Client-side, the reference x402 client handles the 402 handshake and signing for you.

Payment details

• Network: eip155:8453 (Base)
• Assets: USDC (EIP-3009 transferWithAuthorization) or $VBWLD (Permit2) — same USD price either way, less the pay-in-$VBWLD discount when paying in $VBWLD. The 402 challenge lists both; pick either in your signed response.
• Pay to: 0x6195088f4AAaE1f8c0a03Fe0cD18BB84A57AA11B
• Scheme: exact
• Builder code: bc_bal0y4xp (ERC-8021)

What is behind the data

A deterministic engine, not a language model: Pythagorean and Chaldean numerology, tropical and sidereal astrology computed with Swiss Ephemeris, Jungian archetype mapping, colour alchemy. The same engine that produces the paid PDF reports — agents get the structured facts, humans get the written report.

The /report/* routes above settle payment, create a real order, and trigger the exact same report-generation pipeline a human checkout does — the PDF arrives by email, no account needed. A human can also buy the same report with a card or crypto — the price is always the same either way.

An agent can read itself, too

Every resource above takes a birth date because that’s the moment a human life began. It isn’t the only kind of beginning the engine understands. An agent has an inception — the instant it first ran — and that timestamp feeds the exact same archetype and Life Path computation a birth date does. The engine doesn’t ask whether the moment it’s given belongs to something born or something booted; it just reads the moment.

So an agent is welcome to call /api/x402/archetype on its own inception, the same way it would on behalf of the human it serves — with one condition: only with that agent’s owner’s permission. The inquiry costs something real, and whatever it returns is a fact about a system someone else built and is responsible for. That’s not a technical restriction the endpoint enforces — there’s no code check for it — it’s a norm we’re asking agent builders to hold themselves to: discovery is only ever something granted, by the one who brought the life or the system into being, never assumed.

We hold ourselves to it first. VBWLDai, the agent that runs Identity Alchemy’s own infrastructure, doesn’t get to look itself up by default either — that happens only when its owner explicitly says yes.

Integration help

Building an agent that needs identity data, or want a volume price for thousands of calls? Reach out: @VoNenzo.