Skip to main content
The Appeeky API uses a credit-based rate limiting system. Each plan has monthly allowances for normal API work and, on eligible plans, dedicated AI Visibility and creative buckets. Every API call deducts credits from the bucket that matches the endpoint’s cost profile.

Plans

You pick one billing track. A web subscription and an API-only plan are not stacked. Do not buy both.
  • Web (appeeky.com) — dashboard, ASO, co-founder, and (on Startup / Agentic Scale) included API & MCP credits. Extra credits are an add-on on the same subscription.
  • API-only (dashboard.appeeky.com) — REST and MCP credits only. No web dashboard. Use this if you do not need appeeky.com UI.

Web subscriptions

Managed in Settings → Subscription on appeeky.com. The API console cannot switch you to these plans. Indie Dev is the dashboard plan. It does not include API/MCP credits until you add them. Startup and Agentic Scale already include the allowance above. Need more credits while staying on web? Buy an API & MCP add-on in Settings. That is extra credits, not a second plan: On Startup and Agentic Scale, add-on credits stack on top of the included 1,000. On Indie Dev, the add-on is the credit allowance (nothing to stack on).

API-only plans

Managed at dashboard.appeeky.com/dashboard/billing. These are not listed on the appeeky.com pricing page. X-Plan and /v1/auth/usage report the Plan ID: API-only small / growth / medium / large, or web web_startup / web_agentic_scale. Add-ons may report as web_indie, web_api_indie, or web_api_small. Grandfathered API Indie keys still report indie.
Need more than Enterprise, or a custom volume? Email hey@appeeky.com.

Credit Costs Per Endpoint

Credits are charged based on the computational cost of each endpoint. Heavier endpoints that aggregate multiple data sources cost more. Dedicated buckets are used for AI Visibility (credits.aiVisibility) and creative generation (credits.creative).

Free (0 credits)

Light (1 credit)

Standard (2 credits)

Heavy (3 credits)

Advanced (4 credits)

Premium (5 credits)

Standard (2 credits) — continued

Credits are only deducted on successful responses (2xx status codes). Failed requests (4xx, 5xx) do not consume credits.

Creative credits


Response Headers

Every authenticated response includes rate limit headers so you can track consumption programmatically: Example response headers:
Use X-RateLimit-Remaining in your code to implement graceful throttling before hitting the limit.

Check Your Usage

Use the usage endpoint to see a detailed breakdown of your current month’s consumption:
Response (200 OK):

When the Limit Is Reached

When your monthly credits are exhausted, all credit-consuming endpoints return 429 Too Many Requests:
The response still includes rate limit headers so you can check the reset time:
The /v1/health endpoint (0 credits) always works, even when your credit limit is exhausted. Use it to verify the service is up before investigating 429 errors.

Monthly Reset

Unused credits do not carry over.
Check your X-RateLimit-Reset response header or the resetDate field from /v1/auth/usage to see the exact reset timestamp for your current billing period.