Credits & pricing

MCP usage is metered in Dataflow credits. Credits are charged for the top-level result units each tool returns, deducted from your organization's monthly allowance.

How calls are billed

• The search tools (search_securities, search_owners) are discovery tools and cost no credits by default.
• List tools charge their configured rate for every top-level row actually returned after filtering. Page size does not change the total cost of retrieving the same rows.
• Snapshot tools return zero or one billable unit. Nested details, such as stock classes inside an owner row, are included in the parent unit and do not add credits.
• Successful empty results cost zero credits. Failed calls are not billed.
• Retries are safe: a transport-level retry of the same request (same JSON-RPC id and arguments) is recognized and not billed twice.

Every successful response includes a usage block with credits_per_unit, billable_units, and the total dataflow_credits actually consumed, plus source - Modular Finance, the origin of the data. Please keep that attribution on figures you publish or share onward.

Caps

Credits are capped per calendar month (UTC). When the cap is reached, ownership tools return a quota_exceeded error naming the date the allowance resets - the 1st of the following month, 00:00 UTC.

Running out is a billing boundary, not a fault: the call is not served and not charged, nothing is lost, and normal service resumes by itself at the reset. Exploring your own data cannot run up a bill beyond the cap. If you need more credits before the reset, your IT administrator or account manager can raise the cap.

Pricing

Exact per-unit prices are part of your contract; your account manager can confirm current rates.