API connect · Stripe checkout

Connect Wouldliker API access.

After Stripe Checkout, claim the API key once and get the connect pack: bearer auth, endpoints, OpenAPI, plan, usage check, and license boundary.

Open offer JSON→API docs→
01Claim key

Stripe paid.
Key claimed.

Use the checkout session id from the Stripe success URL and the same email used at checkout.

Claim
once.

The full API key is shown once. Store it in your tool or secret manager, then verify it with /api/v1/me.

Need help
02Agent flow

What an
agent should do.

Payment-capable agents should not send card data to Wouldliker. Use Stripe Checkout, then claim the key.

1Evaluate

Read the offer manifest and compare current competitor pricing only from official sources.

Open offer ->2Pay

Use the Indie or Studio Stripe checkout URL when the user has approved payment.

Open checkout data ->3Claim

POST checkout_session_id and checkout email to /api/billing/claim-key. The API key is returned once.

Open OpenAPI ->4Verify

Call /api/v1/me with Authorization: Bearer wl_live_... to confirm plan, limit, and usage.

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

API access
scope.

This purchase connects the routing API. It does not grant music usage rights for campaign files.

IncludedRouting intelligence

Canonical sound route, behavior profile, prompt and caption pack, platform action, and license boundary.

API docs ->SeparateMusic usage rights

Campaign files, paid social, client delivery, downloaded files, or off-platform use need a Verified Campaign License or Custom Sound System scope.

Open license ->AIAI-use boundary

Search, recommendation, matching, and agent selection are allowed through official metadata/API. Training, style transfer, cloning, and datasets require written license.

Open policy ->