Developer API

Plans and rate limits for the AppUo API

AppUo provides authenticated company-intelligence API access through bearer keys. Every workspace is bound to the plan it already owns, so keys, quotas, and request headers all come from the same source of truth.

Public docs live on the apex host. Private issuance, revocation, and quota review live under /workspace/developers.

Request flow

How authenticated access works

api.appuo.in

Step 1

Issue a workspace key

Create or revoke keys from the workspace console. The secret is shown once and stays scoped to the workspace plan.

Step 2

Send bearer auth

Call api.appuo.in with Authorization: Bearer <api_key> on every request. API auth does not use cookies.

Step 3

Watch the limit headers

Respect X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After before retrying.

Plans

Workspace plan determines keys and quotas

The plans below map directly to the existing workspace model. No new subscription schema or request payloads are introduced in this pass.

Free

Proof-of-concept work

Sandbox access for internal evaluation, demos, and very small prototypes.

Active keys
2
Minute
60 / min
Day
1,000 / day
Month
10,000 / month

Starter

First live integrations

Light production access for pilot customers and early customer-facing tests.

Active keys
10
Minute
300 / min
Day
50,000 / day
Month
500,000 / month

Pro

Customer-facing API products

Recommended

The default production tier for teams selling API access to external users.

Active keys
50
Minute
1,000 / min
Day
250,000 / day
Month
5,000,000 / month

Enterprise

High-throughput partner programs

Highest-volume capacity for managed partner programs and larger rollouts.

Active keys
200
Minute
5,000 / min
Day
2,000,000 / day
Month
50,000,000 / month

API promise

Guardrails for v1

AppUo keeps the external contract intentionally small. Bearer auth, plan quotas, and the existing rate-limit headers are the only guarantees this release adds.

  • -V1 stays ops-managed. There is no self-serve checkout or new billing schema in this pass.
  • -The public promise is workspace-scoped bearer auth plus the existing rate-limit headers.
  • -The launch scope stays on the current company-intelligence API family. Other public routes remain untouched.

Launch scope

Focused on company intelligence

This rollout stays on the authenticated api.appuo.in surface and the current company-intelligence family. The anonymous appuo.in/api/v1 routes are left untouched.

What to remember

Use Authorization: Bearer <api_key>, watch the returned rate-limit headers, and keep access linked to the workspace plan you already own.

Chat with AppUo on WhatsApp