Pricing, credits & billing

Predictefy meters API actions in credits. Each plan includes a monthly allowance, a request limit, API-key and WebSocket-stream caps, and a defined product-access level.

Private beta

Private beta — sign up free, no invite required. Every new account starts on the Free plan with 25,000 credits at signup, refilled monthly. Trading ships on every plan, Free included; arbitrage, price-gap (discrepancy) queries, and bulk endpoints start at Builder. Every plan meters all usage in credits, so on Free the monthly allowance is the limit that binds first. Upgrade when you need more volume or the Builder-and-up features.

Public plans

The table below is the settled public plan structure, and it is enforced today. Every new account starts on the Free plan.

Plan	Monthly price	Included credits	Extra 100K	Requests/min	API keys	WS streams
Free	$0	25,000	Not available	60	1	2
Builder	$49	500,000	$8	300	3	20
Pro — Most Popular	$249	5,000,000	$4	3,000	10	100
Scale	$999	25,000,000	$2	10,000	25	500
Enterprise	Custom, $2,500 minimum	Custom	Custom	Custom	Custom	Custom

Pro includes a three-day free trial. Enterprise remains contract-only.

When an available balance is exhausted, requests stop with 402 INSUFFICIENT_CREDITS. Upgrade to a paid plan for a larger monthly allowance, or contact support@predictefy.com if a balance looks wrong. Free has no paid overage unit; Builder, Pro, and Scale can add credits in the plan-specific 100K units shown above.

Feature access

Feature	Free	Builder	Pro	Scale	Enterprise
Historical data	7 days	12 months	Unlimited	Unlimited	Unlimited
Cross-market matching	Limited; results may be delayed	Yes	Real-time	Real-time	Real-time
Price-gap feed	None	Basic	Full	Full	Full
Arbitrage feed	None	Limited	Full	Full	Full
Bulk endpoints	No	Yes	Yes	Yes	Yes
Execution (trading)	Yes	Yes	Yes	Yes	Yes
Commercial use	No	Yes	Yes	Yes	Yes
Support	Community	Community	Priority	Dedicated	Custom

Commercial use is a documentation and terms entitlement. It is not enforced by an API response. Trading ships on every plan: all API keys carry the trade scope by default, with no separate approval or request-access step, and execution is metered in credits like every other action. The remaining tier splits above are enforced — a Free key calling an arbitrage, price-gap, or bulk endpoint gets 403 PLAN_REQUIRED.

The /v1/sql analytical surface is separate from these plans: it requires a dedicated sql scope that no self-serve plan grants. SQL access is available on request — contact support.

Action costs

Action	Credits
Metadata, search, or price snapshot	1
Latest venue metrics (/v1/venues/metrics)	1
Webhook delivery polling	1
Trades or candles	2
Live venue-proxy read — account snapshot, funding requirements or steps, transfer plan, bridge quote, session, or status	3
Order-book snapshot	5
Historical query	5
Existing cross-match lookup	5
Order submission, cancellation, modification, or client-direct acknowledgment	5
Discrepancy qualification	7
Cross-venue comparison	10
Price-gap query	10
Smart-money analytics	10
Cross-venue portfolio valuation (/v1/portfolio)	10
Enterprise SQL (POST /v1/sql)	10
Arbitrage query	15
Fresh AI-assisted cross-match	25

Qualification is priced at 7 rather than the 10 of the comparison class it once shared: one qualification call performs two live order-book reads (3 credits each) plus its own computation. Enterprise SQL is metered like any other action even though the sql scope is provisioned separately. Billing checkout, subscribe, and portal calls are metered at 0 credits — they are recorded as usage but buying a plan costs nothing.

Bulk requests cost the action’s base credits multiplied by ceil(items / 100), with a minimum multiplier of one. For example, 101 order-book snapshots cost 10 credits.

Streaming remains metered at 2 credits per connection-minute, prepaid. The WS-stream value in the plan table limits active logical subscriptions.

Running out

When a balance cannot cover an action, the REST API returns 402 INSUFFICIENT_CREDITS; streaming closes with code 4002. The action is not served, it costs nothing, and the balance is not pushed below zero.

What a failed request costs

Any request answered with a 4xx or 5xx error is refunded automatically and costs nothing. Only served requests (2xx or 3xx) consume credits, and a refunded request records zero credits in your usage.

Requests we reject before metering them at all are never charged: a missing or invalid API key, a missing scope, a plan that does not include the endpoint, a blocked region, a missing Idempotency-Key, and rate limiting.

One related behavior to know: after 3 consecutive 401 VENUE_CREDENTIAL_REJECTED responses on a venue, the platform fast-fails further submits to that venue for 15 minutes instead of re-asking the venue. Like every failed request, those fast-fails are free — fix the credential and the window clears on its own.

A replayed request served from a stored result (Idempotency-Replay: true) also records zero credits — you pay for an action once, not once per retry.

Billing

Self-serve plan and eligible overage checkout use Stripe; Predictefy does not receive card details. Subscription management opens Stripe’s hosted customer portal. Enterprise continues to require a contract.

The developer dashboard’s /usage page shows the current balance, recent usage by endpoint class, and credit-ledger entries.