Credits
Profundis charges credits for searches and selected collection operations. The interface shows your available balance and, where an estimate is offered, the proposed cost before you confirm.
Typical operation costs
| Operation | Default cost |
|---|---|
| Hosts, DNS or certificate search | 1 credit |
| Granular WHOIS search | 3 credits before depth surcharges |
| Unified search, initial query | 1 credit per target dataset, including WHOIS |
| Favicon similarity search | 3 credits |
| ASN lookup | 1 credit |
| Domain overview | Base lookup plus inspected addresses; review the estimate |
| Subdomain enumeration | 1 per 100 returned names for the first 300, then 1 per 300; minimum 1 |
| Bulk search export | 1 per 100 returned rows, rounded up |
| Personal real-time alert delivery | 1 per 10 notifications, rounded up |
These are base rates. Additional pages, grouped views, multi-step tools and optional deeper reveals can have additional charges. Read the price shown for the actual operation. An API call uses the corresponding backend pricing rules; MCP does not make a paid operation free.
Downloading already loaded page results does not rerun a bulk export. A new bulk export has its own estimate and confirmation. Reusing a cached response depends on the operation's cache; do not assume every repeated query is free.
Personal balance
The Free plan includes 50 credits per monthly cycle. Paid allocations and pack prices are listed in the current catalogue; existing subscriptions may have legacy terms.
Monthly credits are used before purchased personal credits. Monthly allocations reset at the account's cycle date; purchased pack credits do not expire. Some offers have their own rollover terms shown at purchase. The credit bar at the bottom of the interface and account billing show your balance and renewal details.
Credit packs
A pack is a one-time purchase rather than a subscription. Choose a pack from Pricing or the credit bar, review checkout, and wait for payment confirmation. Buying a personal pack does not top up an organization. When you create an organization, your purchased personal credits move to it once, after you consent: see What changes for your account.
Organization credits
Research organizations and MSSP client spaces use a shared organization balance. A client's credit envelope limits spending within that balance; it is not an additional allocation. External users can also have a smaller client envelope. Reserved credits cover work in progress and are not available for another concurrent job.
Owners and administrators can inspect the shared balance in the workspace credit bar. Its Credit usage link opens the organization-wide usage report, also in My account → Organization → Credit usage: operations across all clients, grouped by member, operation, client or integration. Other members see the budget they are permitted to use and their current client's usage. If an envelope or organization balance runs out, the operation stops; it never falls back to a member's personal credits or silently bills an overage.
Scheduled research monitoring uses collection credits within its saved limit. Reading an existing change or rendering a report from saved evidence does not run a new search. See Organization billing and Monitoring.
Staging Exposition organizations with capacity billing use scope and asset capacity instead of a per-scope credit envelope. Creating a scope starts an observation refresh from existing datasets within that capacity; reading the stored inventory or a saved report does not spend personal credits. Scheduled asset monitoring follows the organization's active capacity and settings. Legacy Exposition organizations can still use credit billing: consult the workspace's displayed billing model and limits. This distinction does not announce a new price or grant access beyond the organization's subscription. See Exposition contracts.
Out of credits
The interface identifies the exhausted balance or limit. Buy the appropriate pack, adjust an envelope if authorized, or wait for renewal. More credits do not grant access to a dataset or capability excluded from your plan.
API credit-state contract
The browser reads personal balances through /api/v2/auth/credits and current-cycle usage through /api/v2/auth/credits/usage. These session endpoints are separate from the key-authenticated data API; see Session contracts. MCP usage is included in total usage, not added on top.
Staging catalogue vulnerability enrichment and result badges do not consume search credits. Starting a related CVE, KEV or badge-evidence search uses ordinary search pricing and access rules. Search and vulnerability associations describes their availability and limits.
On staging, available Free monthly credits can also pay for personal web UI WHOIS searches. A granular WHOIS search starts at 3 credits; unified WHOIS costs 1 credit for that dataset on the initial query or an additional page. The server debits the full cost before reading data: one remaining credit is enough for unified WHOIS alone, but not for a granular WHOIS search. Field/query validation and counts do not return rows or charge search credits. A zero balance retains the public preview. This change does not grant CPE access or change personal API, export, Pivot, pipeline, IP intelligence or organization permissions.