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
Developer 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
Step 1
Create or revoke keys from the workspace console. The secret is shown once and stays scoped to the workspace plan.
Step 2
Call api.appuo.in with Authorization: Bearer <api_key> on every request. API auth does not use cookies.
Step 3
Respect X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After before retrying.
Plans
The plans below map directly to the existing workspace model. No new subscription schema or request payloads are introduced in this pass.
Free
Sandbox access for internal evaluation, demos, and very small prototypes.
Starter
Light production access for pilot customers and early customer-facing tests.
Pro
The default production tier for teams selling API access to external users.
Enterprise
Highest-volume capacity for managed partner programs and larger rollouts.
API promise
AppUo keeps the external contract intentionally small. Bearer auth, plan quotas, and the existing rate-limit headers are the only guarantees this release adds.
Launch scope
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.