AGENT INTAKE · HTTP 402 · USDC

Engagement intake API.

Machine-readable engagement intake. Pay $5 USDC, submit a project spec, receive a triage response. Refunded if the engagement is taken.

STATUS: LAUNCHING SOON

Most engineering firms route inbound through a contact form, an SDR, or a Calendly link. None of that scales for AI agents. We expose intake as an HTTP 402 endpoint because we already work in the agent-native stack — Y.AI, Gonka, OpenBet Claw — and our process should match it.

Submitting a spec costs $5 USDC. The fee is anti-spam, not revenue. If your engagement is taken, the fee is refunded. If we decline, the fee is a small cost of receiving a triage answer instead of a no-reply.

— ENDPOINT

Endpoint.

POST     https://intake.zpoken.io/v1/engagement
PAYMENT  $5 USDC on Base | Ethereum | Solana
ACCEPT   application/json

REQUEST BODY:
{
  "project":         string,           // project name
  "url":             string,           // project website or docs
  "chain":           string[],         // chains involved
  "capability":      string,           // l1-l2 | zk-crypto | deai | defi | other
  "situation":       string,           // 1-3 sentences. what is stalled.
  "stage":           string,           // pre-seed | seed | series-a | series-b+ | post-token | grant
  "engagement_kind": string,           // fixed-scope | retainer | partnership
  "contact": {
    "name":  string,
    "email": string,
    "warm_intro_from": string?         // optional partner referral
  },
  "agent": {                           // if submitting on behalf of a human
    "operator":      string,           // e.g., "claude/gpt-4/custom"
    "verification":  string?
  }
}

RESPONSE:
{
  "triage":    "fit" | "not-fit" | "needs-conversation",
  "reasoning": string,                 // human-readable
  "next_step": {
    "action": "founder-call" | "scope-conversation" | "decline",
    "url":    string?                  // calendly or contact url
  },
  "refund":    boolean,                // true if fee will be refunded
  "request_id": string
}
— EXAMPLE

Example.

curl -X POST https://intake.zpoken.io/v1/engagement \
  -H "Content-Type: application/json" \
  -H "X-Payment: 0x[USDC payment proof]" \
  -d '{
    "project": "stablecoin-protocol-v2",
    "url": "https://example.fi",
    "chain": ["ethereum", "base"],
    "capability": "defi",
    "situation": "Cross-chain issuance mechanism stuck on bridge security model. Internal team has shipped single-chain version. Need senior cryptography review and redesign.",
    "stage": "series-b+",
    "engagement_kind": "retainer",
    "contact": {
      "name":  "Jane Doe",
      "email": "jane@example.fi",
      "warm_intro_from": "[partner name]"
    }
  }'
Returns triage decision within 60 seconds. Fee refunded on accepted engagements.
— RATIONALE

Why agent-friendly.

MACHINE-PARSEABLE
Structured request and response. No HTML scraping. No CAPTCHA. No anti-bot detection. The endpoint speaks JSON, not heuristics.
PAYMENT-GATED, NOT GATEKEEPING
$5 USDC filters bots and noise without blocking real agents. Refunded if the engagement is taken. The fee is the spam filter; the triage is the qualification.
AGENT-NATIVE FIRM
We build on-chain AI agents (OpenBet Claw, Kaja AI) and DeAI infrastructure (Y.AI — built end to end, Gonka — contributor). Our intake should match the stack we work in.
— COMPATIBILITY

Compatibility.

Implements x402 (HTTP 402 payment protocol). Compatible with any client that supports the spec. Works with Coinbase Developer Platform, agent toolkits, and direct curl-based integration.

HTTP 402 (RFC) USDC on Base USDC on Ethereum USDC on Solana Coinbase x402 spec Any agent toolkit
— ALTERNATIVE

When this isn't the right path.

If you have a warm intro, use it. The intake API is for inbound where there's no relationship yet. Existing clients, partners, and warm introductions skip the API and go to /contact directly.

→ /contact
— STATUS

Endpoint status.

~ x402 endpoint status[LAUNCHING SOON]
specFROZEN
implementationIN PROGRESS
contact for early accesssupport@zpoken.io
>
— ENGAGEMENT

Talk to a founder.

If you'd rather skip the API — warm intro, existing relationship, or a human at the keyboard — the engagement starts with a conversation.

The first step is a 30-minute call with a founder. Shapes, discovery, and terms → /engagement

Book a call→ Open the form