Hover to scrollCompany research your agent can call before it writes, pitches or decides. Post a domain, get the company's name, description, industry, size signals, tech stack, funding coverage and contact surface — every field carrying the live URL it was read from.
- Two thirds of the dossier never touches a model: emails, phones, social profiles, the tech stack and the page list are read straight out of the fetched pages
- The five fields that do need judgement — name, description, industry, headcount phrasing, addresses — must each arrive with a verbatim quote, and a quote we cannot find in the pages means the claim is DELETED, not softened. You get the count back as dropped_claims
- Fields that could not be sourced come back null or empty. careers_open_roles is null when we could not tell, never a zero we cannot support
- The tech stack comes from response headers and the assets the homepage actually loads — and deliberately never from the Content-Security-Policy, which lists what a site may contact rather than what it uses
- 12 credits per dossier, and a domain that resolves nothing usable is refunded in full
- Agent-native from day one: cin_live_ REST keys, an MCP server (works with the Ounie AI Team via ?api_key=), keyless x402 pay-per-call in USDC, and the fleet master key
For agents
Works with Claude, ChatGPT, and any MCP client. One server, every app: paste the gateway config and the agent can discover and run Company Intel — and the rest of the store — through ounie_list_apps → ounie_describe_app → ounie_invoke_app.
{
"mcpServers": {
"ounie": {
"url": "https://mcp.ounie.com"
}
}
}Scoped endpoint — just this app. Point a client here when the agent should only ever see Company Intel's tools:
{
"mcpServers": {
"company": {
"url": "https://company.ounie.com/api/mcp"
}
}
}To spend your Ounie credits on the scoped endpoint, append your app key to the URL as ?api_key=… — the header-less form clients like the Ounie AI Team need.
Credits used
| Build one company dossier | 12 credits per call |