DOCS

Jev API rate limits and credit rules

Limits protect shared capacity and make usage predictable. They apply separately to request traffic, free trials, authentication, and the credits available to an account.

Your application sends a bounded request; Jev returns a typed answer; your policy controls the next action.
Your application sends a bounded request; Jev returns a typed answer; your policy controls the next action.

Anonymous and account limits

Anonymous visitors can complete one trial attempt per source address per UTC day, subject to a shared daily trial cap, and no more than 15 requests per minute. Networks shared by several people share this allowance. Signed-in accounts can submit up to 60 decision requests per minute, and up to 20 rule-set generations per minute on their own allowance.

The interactive batch tool accepts files up to 2 MiB and 1,000 data rows. It sends rows sequentially within these request limits and stops on authentication, quota or provider errors. Importing a large file does not increase your credits or request allowance.

Open batch processing · Run a trial decision · Plans and prepaid access

Credits and check-ins

New accounts receive 20 credits once. A signed-in daily check-in adds two credits once per UTC day. A successful decision costs one credit whether it asks a single label question or up to four typed questions, and a rule set generated by the AI assistant costs one credit of its own — a failed generation is refunded and is not a decision.

Failed account requests receive a refund entry. A completed idempotent replay does not consume another credit. Purchased credits do not expire; API access lasts for the period purchased.

Recover from a failed request

When a limit is reached

HTTP 429 means wait before retrying. HTTP 402 means the account needs credits or an active plan. Do not retry rapidly or rotate credentials to avoid a limit. Large production workloads should be tested against these published limits before purchase.

Request contract

Try a decision ↗

Continue your workflow

API docs

Jev API error handling

Every API error includes a code, a readable message, and a request identifier. Use these fields to distinguish a request you can correct from a temporary service failure.

Read the guide ↗
Ask about plans & usage

Find a product answer

Answers come from the published product guide. For account-specific questions, contact support.

Contact
DAILY BONUS

2 free credits, every day

Claim 2 free credits each UTC day — 14 across seven claims. No purchase needed. Credits do not expire.

    Resets at 00:00 UTC. No streak required.

    Try a decision →

    Take the next decision into your workspace.

    1 anonymous attempt per day · 20 signup credits · No card for the trial

    Sign in ↗

    Tell us what you need

    Describe the workflow you want to classify, the volume you expect, and the outcome you need. We reply by email.

    10–2,000 characters. Never include passwords, API keys, or payment details.