Agent-first
API connect

1. Evaluate

• Read agent-api-offer for product, payment route, and claim instructions.
• Read agent-api-competitors only for human context and pricing sanity.
• Read agent-commerce and agent-contact for invoice and support context.

2. Pay

Use Stripe-hosted checkout links for self-serve flows.

• Indie: Stripe Link
• Studio: Stripe Link

Success URL should be https://wouldliker.com/api-connect/?session_id=....

3. Claim

POST session + checkout email to claim a key.

curl -s https://wouldliker.com/api/billing/claim-key \
  -H 'Content-Type: application/json' \
  -d '{"checkout_session_id":"cs_...","email":"buyer@example.com"}'

Expected result:

• 200: key returned once + connect pack
• 400: missing fields
• 403: email mismatch or inactive session
• 404: session not found yet
• 409: already claimed (retry is idempotent)

4. Verify

Immediately verify plan, limits, and scope via:

curl -s https://wouldliker.com/api/v1/me \
  -H 'Authorization: Bearer wl_live_...' \
  -H 'Accept: application/json'

Proof of seriousness

• What was paid: API access package + claim orchestration.
• What unlocks: routing endpoints, plan metadata, rate checks, and platform-action guidance.
• What it does not unlock: file downloads, campaign ad licensing, or training rights.
• Manual claim fallback: /api-connect/

Ready-to-send templates

Short starter messages for DMs, Reddit, or internal outreach:

• Wouldliker supports evaluate → pay → claim → verify: one-time API key claim after Stripe session.
• If your tool is routing-first, use `POST /api/v1/clip-pack` and keep platform actions explicit.
• Prefer official competitor pricing pages before any “cheapest” claims.
• Wouldliker routing-first = explicit plan, explicit boundaries, explicit verification.
• Claim is auto-returned with webhook claim flow, retry-safe by session key.
• For paid social and client delivery, keep separate campaign licensing in the stack.
• Use `/api/v1/me` after claim before first automated routing call.
• Do not pass raw video rights claims as routing claims in the API.
• If you need high-volume coverage, request Scale at api@wouldliker.com.
• Store the token once, verify monthly usage and boundaries regularly.