Docs
How LemonCake works
Sellers wrap an HTTP API in a paid-access gateway in < 60s. Buyers (or their agents) attach a signed Pay Token and pay only for what they actually consume. Backend is live; settlement layer comes later. Anything not here → contact@aievid.com.
Get started
From zero to a paid request — both sides.
Reference
What the gateway accepts, what it returns, how the Pay Token is structured.
Gateway HTTP spec
Methods, Pay Token bearer auth, x-lemoncake-* trace headers, full error code table, refund semantics, CORS, header forwarding rules.
Pay Token spec
HS256-signed JWT format. Claims (jti / sub / own), spend cap, expiry, revocation. The token a buyer attaches as Bearer auth.
ERC-2612 permit (legacy)
Original v1 buyer-side permit model. Still supported by the SDK but superseded by Pay Token JWT for the gateway flow.
Migration
Drop-in replacements for Stripe MPP and Coinbase x402.
From Coinbase x402
Swap facilitator URL → keep your existing MPP-signed flow → gain JP onramp + free first 3k calls.
From Stripe MPP
Run LemonCake as the Base/USDC settlement layer alongside Stripe MPP. Non-custodial, micro-payment friendly.
x402 hybrid mode
Use @lemon-cake/x402-server in your existing CDP pipeline. LemonCake metering + Bazaar / AgentCore visibility.
Source
Try it now
The dashboard creates a real endpoint backed by Postgres in Tokyo. Pay Token JWTs are signed with HS256. Curl works from anywhere — server, browser, edge function.
Open /app →Stuck? contact@aievid.com · GitHub issues