Skip to main content
The contract version is 2026-10-19. The published credit plan for new signups is datalayer_credits_v2. A response reports the account’s own credit version. See credit rates and exact bounds. REST and hosted MCP execute through the same authenticated API and atomic ledger. meta.credits_used reports the new deduction caused by this invocation, not your remaining balance. meta.receipt retains the authoritative original reservation, settled items and released amount. On idempotent replay credits_used is zero while the original receipt remains unchanged. meta.lookup_requests is the lookup count and is zero on cached replay. meta.upstream_requests is the deprecated alias of that count. A dry-run estimate reports lookup_calls as 0; provider_calls is the deprecated alias. profiles_used is deprecated compatibility metadata and is 0 on credit responses. Use credits_used. Call get_account_details for balance.

Maximum estimate and budget

Pass dry_run: true to validate inputs and return a maximum estimate with no data lookup and zero debit. Pass max_credits from 0 through 3 to cap a real profile, search, job or email request. A profile with a verified work email can need 3 credits on the published plan for new signups. build_list accepts max_credits from 0 through 100 because it reserves 1 credit per 100 requested IDs, rounded up. Its record IDs are stored on the export job, not in the 64KB credit receipt. When the permitted maximum cannot be reserved, the request is rejected before any data lookup. Known eligible repeats reduce the reservation; an unresolved identity may require the full maximum until its canonical reference is known. Reservation, delivered-item settlement and unused release are atomic in D1. Revoked/expired funding cannot settle. Failed requests release their holds; abandoned holds are recovered. Lookups are bounded to eight per operation, 40 seconds and a 1.5MB response. Normalized saved responses are bounded to 64KB. Internal lookup counts never create extra customer charges.

Recover a lost response

Send Idempotency-Key with every paid operation. Keep the same operation and normalized input on retry. A committed credit result is replayed from persisted normalized data, without another data lookup or charge. Changed input, an expired key or an expired paid anchor returns idempotency_conflict. A request still in flight returns request_in_progress; retry that same key later. Network delivery and D1 commit cannot be made atomic. A timeout alone does not prove zero usage. Retry the key and inspect the receipt/dashboard before starting a new paid request. The paid repeat window is 24 hours and does not slide. Saved dashboard details and single-result exports last 90 days and cost zero. Deleting a saved copy removes its replay bytes without erasing accounting. Allowances previously counted in profiles are the same number of credits.