← Back to docs
Guides
GUIDEQuota and usage behavior
Quota and usage guide
This guide explains how Entylink enforces monthly quota, how to read usage, what happens at quota exhaustion, and where the unauthenticated demo endpoint has a separate IP-based limit.
When to use it
Practical implementation contexts
Show quota bars and upgrade prompts in account surfaces
Decide how your app should react to quota exhaustion
Separate production API usage from the public demo endpoint's IP limit
Auth
Access model
Authentication
Quota checks run after authentication on protected data routes. Usage summary itself requires a dashboard session.
Usage and limit examples
# Read current account usage
curl https://api.entylink.com/v1/usage \
-H "Authorization: Bearer etl_session_..."
# Public demo lookup is separate and IP-limited
curl https://api.entylink.com/v1/demo/company/08804411
Usage payload and quota-exceeded response
Usage summary + 402 exampleReference
Usage summary:
{
"data": {
"plan": "PROFESSIONAL",
"monthly_quota": 250000,
"current_month_usage": 18231,
"daily": [
{ "day": "2026-04-22", "count": 1843 }
]
}
}
402 quota_exceeded:
{
"error": "quota_exceeded",
"message": "Monthly quota of 250000 requests reached. Upgrade your plan.",
"upgrade_url": "https://entylink.com/pricing",
"status": 402
}Related pages
Keep moving from docs into implementation and evaluation
Next step
Move from docs into a real registry workflow.
Entylink is built for teams embedding UK company data, verification, and monitoring into products rather than manually browsing the register.