Build a sourcing agent in minutes.
Clous exposes a hosted remote MCP server over the same API. Your agent gets typed tools that return resolved entities — no query DSL, one consistent envelope, cursor pagination, and the credit cost surfaced on every call.
Get an API key
Sign up and copy your key from the dashboard. Keys look like clous_live_…. New accounts start with 100 free credits (verified companies).
Connect the MCP server
Add Clous to your MCP client config (Claude, or any MCP-compatible agent). The key is passed at connect.
{
"mcpServers": {
"clous": {
"type": "http",
"url": "https://mcp.clous.ai",
"headers": { "Authorization": "Bearer clous_live_…" }
}
}
}Call typed tools
Every tool returns the same envelope. Every record carries entity_id, confidence, and as_of.
# "Find new 506(c) raises over $5M in fintech,
# resolve each issuer's domain + founders."
raises = search_form_d(sector="fintech", # 5 credits
is_506c=True, min_amount=5_000_000,
new_only=True)
for r in raises.data:
entity = get_entity(r.entity_id) # 2 credits each
print(entity.domain.value, entity.people)Discover everything via llms.txt
A machine-readable summary of the product, API base, MCP endpoint, auth, URL patterns, credit costs, and example queries lives at clous.ai/llms.txt. The OpenAPI 3.1 spec generates the docs and the MCP tool schemas, so the three never drift.
Available tools
tool · cost* shipping as the underlying source goes live. See full credit costs on pricing.
Try the tools without writing code
The dashboard playground runs any tool, shows the JSON envelope, and copies the call as cURL / Python / JS / MCP.