Rate Limits & Credits

Two limits apply to your organization, shared by all of its API keys:

Credits set how much you can do. Each action costs a fixed number of credits, drawn from one balance.
Rate limits set how fast you can do it, in requests per minute.

Credits

Each action has a fixed price. Get Credit Pricing lists every price:

curl "https://api.signa.so/v1/credits/pricing" \
  -H "Authorization: Bearer sig_YOUR_KEY"

Get Credits returns your balance and reset date. Plans and extra credits are on the pricing page. How billing works:

Searches are billed per page. Record reads are billed per request: one record, or one page of a list such as an owner’s trademarks. A batch lookup costs one credit per submitted identifier, including the ones returned in not_found.
Only successful responses are billed, including 304 Not Modified and empty pages. Errors are never billed.
Offices, jurisdictions, event types and your account endpoints are free.
Managing watches, alerts and webhooks is free. Watches and managed marks are billed per day instead.
Beta actions, such as screening and compare, are free during the beta.
An MCP tool call costs the same as the API request it makes.

Paid plans can spend up to 25% of their monthly credits per UTC day, and the Free plan up to 5,000. This stops a runaway script from draining a month of credits in minutes. Enterprise has no daily cap.

Rate limits

Rate limits are requests per minute, set by your plan:

Plan	Most endpoints	Screening and compare	Deadline computation, goods and services drafting and validation
Free	60	30	30
Starter	300	30	30
Growth	1,000	100	1,000
Scale	3,000	300	3,000
Enterprise	Custom	Custom	Custom

Each type of endpoint has its own budget, so heavy searching doesn’t slow down record reads. POST, PATCH and DELETE requests are also capped at 1,000 per minute. Searches with mark_text_contains, mark_text_ends_with or a pattern starting with a wildcard can run at most 4 at a time per organization. If you need higher limits, contact support@signa.so.

Response headers

A search request on the Free plan returns headers like these:

HTTP/1.1 200 OK
RateLimit-Policy: 60;w=60, 10000;w=60
RateLimit: remaining=54, reset=30
X-Credits-Charged: 10
X-Credits-Remaining: 940
X-Credits-Limit: 1000
X-Credits-Reset: 2026-11-01T00:00:00.000Z

Header	Description
`RateLimit-Policy`	The limits and their window in seconds: your plan’s limit for this type of endpoint first, then the overall ceiling for this kind of request (reads or writes).
`RateLimit`	Requests remaining and seconds until the window resets.
`Retry-After`	Seconds to wait before retrying. Only on `429` responses.
`X-Credits-Charged`	Credits this request cost.
`X-Credits-Remaining`	Credits left in your balance.
`X-Credits-Limit`	Credits granted this period, including any you bought.
`X-Credits-Reset`	When your monthly credits refresh (ISO 8601).

Publicly cached catalogue responses (such as classifications and fees) leave these headers out. A missing header doesn’t mean the request was free.

Handling 429

A 429 response has one of three error types:

Type	Meaning	What to do
`rate_limited`	Too many requests per minute, or too many searches running at once	Wait `Retry-After` seconds, then retry.
`daily_credit_cap_exceeded`	Daily credit cap reached	Wait until UTC midnight, or upgrade.
`insufficient_credits`	Credit balance used up	Buy credits or upgrade. Retrying fails until the balance changes.

The TypeScript SDK retries rate_limited responses for you.

Overview

Trademarks

Parties

Records

Intelligence

Filing & docketing

Monitoring

Analytics

Reference

Administration

SDK

Rate Limits & Credits

Credits

Rate limits

Response headers

Handling 429

​Credits

​Rate limits

​Response headers

​Handling 429

Credits

Rate limits

Response headers

Handling 429