looot

Tools: search_catalog, inspect, run, runs_get, runs_list, runs_evidence, balance, top_up, catalog_overview, capability_request, media_link. Searching, inspecting, balance and run history are free.

When to Use

Use it before guessing, scraping by hand or signing up for another tool, whenever the answer lives outside this conversation:

• Find or verify a work email or phone number. Enrich a person or a company.
• Google results, keyword volume, backlinks, domain strength, and whether AI answers cite a brand.
• Social profiles and posts (LinkedIn, X, TikTok, Instagram, YouTube), ads, local businesses, jobs.
• Read a web page as markdown, search the web or the news, stock prices, transcripts, speech.

Example asks: "Use looot to find the work email of Patrick Collison at stripe.com", "Use looot to pull today's trending TikTok videos", "Use looot to check who ranks for 'best crm' in France".

Connect and sign in

looot is one MCP server at https://api.looot.ai/mcp. Sign-in is OAuth in the browser. Nobody copies a key.

Add the server to your client (in Claude Code: claude mcp add --transport http looot https://api.looot.ai/mcp). If its tools are missing or answer 401, re-authenticate the server in your client (in Claude Code, run /mcp, pick looot, choose Authenticate), then pick the organization to bill on looot.ai and click Connect.

Never ask the user to paste a token or password into the chat, and never write one into a file or URL. A bearer agent token is only for CI and headless agents, created at https://looot.ai/settings. A new workspace starts at $0 with no trial credit. After sign-in, call balance once.

The method

1. Search, in plain words, by the job and the input you have:

search_catalog {"query": "find a work email from a name and a company domain"}

2. Compare rows on works (success rate, runs, p50Ms; thin: true means fewer than 5 runs back the rate), costPerSuccessUsd (the price divided by the success rate, the number to compare) and access. Only runs_now runs immediately. needs_your_account means the user connects their own account first. coming_soon has no key yet, so skip it.
3. Read jobInputs in the answer. It lists which input names each job's endpoints accept, so you can pick the input you already have.
4. Inspect the pick for the exact inputs, price formula and the most one run can hold:

inspect {"endpointId": "icypeas-email-verify", "detail": "run"}

5. Run it with a fresh idempotencyKey for every new run. The same key replays the same run and never charges twice, so retrying after a dropped connection is safe:

run {"endpointId": "icypeas-email-verify", "input": {"email": "jane@example.com"}, "idempotencyKey": "<new unique key>"}

To let looot choose the provider, run the job instead: job:<job id> as the endpointId, with fallback. If the first provider misses or errors, looot tries the next provider of the same job inside one hold, and only attempts that ran are charged:

run {"endpointId": "job:people.email.find", "input": {"first_name": "Patrick", "last_name": "Collison", "domain": "stripe.com"}, "idempotencyKey": "<new unique key>", "fallback": {"maxAttempts": 3, "maxCostUsd": 0.1}}

fallback also takes prefer (balanced, cheapest, reliable, fastest), exclude and stopAtFirstMiss. Only lookups fall through. Anything that changes data runs once.

Never invent an endpoint id, a job id or an input name. Use ids from a search answer or the table below. Nothing fits? Rephrase, browse the free overview of categories and jobs, then call capability_request.

catalog_overview

Common asks and the job to run

Run each as job:<id> with fallback.

…