QuantaAPI
Dashboard
Reference

Limits and current scope

What QuantaAPI supports today, what it deliberately does not, and what the free beta means.

Free beta
3 min read

QuantaAPI is in beta and free to use. This page lists the boundaries so you do not design against something that is not there yet.

Free and unmetered

  • No plans, subscriptions, or billing.
  • No request quota and no per-collection or per-endpoint limit enforced by the product.
  • No feature gating: every account can use every feature described in these docs.
No rate limiting todayRequests are not throttled by the platform. A 429 response only appears if you put a 429 entry in the error pool and simulation triggers.

Technical limits

Endpoint type
REST only
Response format
JSON object
Path matching
Exact, no dynamic segments
Path length
Up to 200 characters
Latency
0 – 5000 ms
Log page size
15 entries
Log history
Last 7 days in the chart; logs kept until the endpoint is deleted

Not supported yet

  • GraphQL or WebSocket endpoints.
  • Team workspaces, roles, or shared ownership — every collection belongs to one account.
  • Custom domains.
  • Search across documentation or endpoints.
  • Nested body validation; only top-level fields are checked.
Known gap: the `object` field typeThe data requirement editor offers an object field type, but the API only accepts string and number. Saving a requirement that contains an object field is rejected. Use string or number until nested objects are supported.

Data retention

Request logs are stored with their endpoint. Deleting the endpoint deletes its logs; deleting the collection deletes its endpoints and their logs; deleting the account deletes everything. There is no separate retention window.