Costs, limits & long-running jobs

AI budget

Using the connector itself is included in paid plans. Some tools also spend AI budget: the shared AI usage quota of your workspace for the current billing period, the same one the kōdlo web app uses.

Tool	Cost
kodlo_discovery_start	Charged by the work a discovery run does
kodlo_research_start	Charged by the work a research run does; deeper runs cost more
kodlo_lookup_contact	Cents. Capped at 6 searches and 3 page reads per run
kodlo_enrich_contact	Tens of cents per contact. A focus roughly doubles it, and each extra platform is a separate paid lookup. A batch (contact_ids) costs about half as much per contact
kodlo_search_knowledge, meaning search in kodlo_search_conversations	A small amount per query

Every other tool is free.

• kodlo_whoami and kodlo_discovery_prepare show how much of the budget is used.
• Usage is recorded during a run. If a run is cancelled or fails part-way, the work already done is billed.
• When the budget for the period runs out, paid tools are refused until the next period or a plan upgrade.
• A workspace with a failed payment cannot start new paid work until the payment method is updated.
• Workspaces that use their own AI provider keys pay those providers directly.

Background operations

Discovery, research, lookup and enrichment run in the background:

1. The start tool returns an operation id straight away.
2. Claude checks it with kodlo_get_operation, about once a minute. Lookups take about 15 seconds, enrichment about a minute, research 5–30 minutes, and discovery from a few minutes up to about an hour.
3. When it succeeds, the result has the ids of what was produced and a suggested next step.

Each finished run also appears in your kōdlo archive as a conversation from MCP, and you get a notification in the web app.

One run of each kind per person. You can have one discovery, one research, one lookup and one enrichment running at the same time, but not two of the same kind. Starting a second returns the id of the run already in progress. A discovery or research run you started in the web app counts too.

Cancel with kodlo_cancel_operation. A queued run is cancelled with nothing spent. A running one stops within about 30 seconds.

Runs interrupted by a kōdlo update or restart are not retried automatically. Start them again when you are ready.

Rate limits

Per API key:

Limit	Value	When it is exceeded
All calls	120 per minute	HTTP 429: Too many requests for this API key.
Calls that change data	30 per minute	Tool error rate_limited. Wait a minute, then continue.

Size limits

Item	Limit
Contacts per kodlo_create_contacts call	50
Contacts per batch enrichment	25
Discovery accept / reject per call	200 each
Markdown document	2 MB
File upload to Knowledge Hub	10 MB
Timeline event content	10,000 characters
Ticket comment	10,000 characters
Event comment	1,000 characters
Report / document text per page	20,000 characters

Data retention for operations

Finished operations, including their input and results, are kept for 30 days and then deleted. Retry records for client_request_id are kept for 7 days. Reports, contacts and documents the operations produced follow your workspace’s normal retention.