REST API · v1

One predictable path across five products.

Every request is authenticated by the same verifier and authorized against one exact product operation attached to the key.

Authentication

Send the one-time key from the developer console in the Authorization header. Query-string credentials are rejected. Key creation requires an environment, expiry, REST/MCP transport choice, rate limits, and an explicit review.

curl https://api.baiseapps.com/v1/casa/capabilities \
  -H "Authorization: Bearer $BAISE_API_KEY"

Product identifiers

legalmdcasainfluencertech

A key can hold any explicit subset of 20 product-operation permissions. Access to one product or operation never implies another.

Endpoints

GET/v1/{product}/healthPublic service check

GET/v1/{product}/capabilitiescapabilities:read

GET/v1/{product}/providersproviders:read

GET/v1/{product}/requestsrequests:read

POST/v1/{product}/requestsrequests:write · production keys only

DELETE/v1/keyEmergency self-disable, when enabled at creation

Download the OpenAPI document →

Errors and limits

401 is intentionally generic for missing, malformed, unknown, expired, transport-blocked, IP-blocked, or quota-exhausted credentials. 403 means the authenticated key lacks the exact operation scope. 429 includes Retry-After.