Jev pricing, rate limits, models, and SDK versions
Verified 2026-09-30: compare TypeSafe direct API, Vercel AI Gateway, and Cloudflare Workers AI pricing, context, limits, tested package versions, and newer upstream releases.
Jev does not have one channel-independent price or limit
TypeSafe direct API, Vercel AI Gateway, and Cloudflare Workers AI are separate access channels. Verify price, context, credentials, and quotas per host/provider. An unknown below means the reviewed public source did not publish the value—not zero and not unlimited.
Keep price and limits separated by channel
TypeSafe direct API
api.typesafe.ai- Model
jev-1.13.0alias jev-latest- Input price
- $0.042 per 1M input tokens ($42 per 1B)Published direct-API price
- Output price
- Free
- Context
- 64k tokens per request; state plus longest question limited to 32k
- Token rate limit
- 100,000 tokens per second
- Request rate limit
- 40 requests per second
- Account quota
- unknown — not published in the public docs reviewed
Vercel AI Gateway
Vercel AI Gateway- Model
typesafe-ai/jev- Input price
- Starting at $0.04 per 1M input tokensGateway listing; provider table showed TypeSafe AI and DigitalOcean
- Output price
- unknown — not displayed on the reviewed model page
- Context
- 32K in the reviewed provider table
- Token rate limit
- unknown — not published on the reviewed model page
- Request rate limit
- unknown — not published on the reviewed model page
- Account quota
- unknown — depends on Gateway account and provider terms
Cloudflare Workers AI
env.AI binding / api.cloudflare.com- Model
typesafe/jev- Input price
- $0.042 per 1M input tokensCloudflare model-catalog token equivalent; Workers AI bills neurons in the back end
- Output price
- $0.00 per 1M output tokens
- Context
- 32,000 tokens in the reviewed model catalog
- Token rate limit
- unknown — no Jev-specific token rate published on the reviewed pages
- Request rate limit
- 300 requests per minute default for Text Generation unless a model requires Workers Paid
- Account quota
- 10,000 Neurons per day free allocation across Workers AI; paid overage requires Workers Paid
Latest upstream is not the same as tested here
| Package | Tested here | Latest observed | Runtime | Status | Published |
|---|---|---|---|---|---|
@typesafe-ai/sdk ↗npm | 0.6.0 | 0.6.0 | Node >=20 | Tested = latest observed | |
typesafe-sdk ↗pypi | 0.7.2 | 0.7.2 | Python >=3.10 | Tested = latest observed | |
langchain-typesafe ↗pypi | 0.0.1a3 | 0.0.1a3 | Python >=3.10,<4; pre-release / beta | Tested = latest observed | |
langchain-core ↗pypi | 1.6.6 | 1.6.6 | Python >=3.10,<4 | Tested = latest observed | |
@ai-sdk/gateway ↗npm | 4.0.101 | 4.0.101 | Node >=22 | Tested = latest observed | |
ai ↗npm | 7.0.123 | 7.0.123 | Node >=22 | Tested = latest observed | |
@ai-sdk/typesafe-ai ↗npm | not tested | 3.0.11 | Node >=22 | Observed, not tested here |
This site never rewrites examples merely because a registry has a newer release. “Behind” requires a changelog review, lockfile update, and complete contract/browser rerun. “Not tested” records discovery, not compatibility or endorsement.
Do not infer what the public pages do not say
- Gateway request rate, token rate, and account quota.
- The final bill under different accounts, contracts, regions, or promotions.
- Whether a newly published package works with these examples before a pinned test run.
- Whether price, limits, context, or aliases will remain unchanged.
Check upstream drift before shipping
The repository’s read-only monitor checks official-page markers, docs sitemap lastModified values, and npm/PyPI latest versions plus runtime constraints. It reports changes; it never edits prices or upgrades dependencies.
npm run seo:upstream- If the result is current, still confirm model access and billing terms in the real account.
- If it reports drift, read the primary change before updating the snapshot, page, examples, or lockfile.
- Any factual number change updates the verification date and reruns all gates; never refresh the date alone.