Trade intelligence for AI agents.

In our internal benchmark, a trusted lead costs $1.45 and takes about 22 seconds with EximAgent, versus $5.50 and 70 seconds for the same AI agents working alone, and $5.12 against a modeled 12-minute-per-lead manual baseline. The quality gap is wider than the speed gap: 96% of EximAgent-assisted leads passed the trust check, versus 56% for independent agents. The setup was deliberately hard on us — 180 standard companies, three repeated runs, and the companies' websites hidden from the agents, so the numbers measure the indexed data layer rather than an agent's ability to browse. Behind those results sit 276 million-plus shipment records from official customs sources and 578,000-plus identified importers, with 82% of enriched companies yielding a verified contact. Corpus depth varies by trade lane, and every query reports its own coverage envelope.

Installing the CLI and creating an account are free — you pay only for what you run. Billing is usage-based per command: anything billable shows a cost preview first and waits for your explicit confirmation, so a run never charges you without showing its scope and price up front. Bulk jobs preview the same way, which is how you confirm the cost of a few-hundred-company run before it starts. Read-only HS-code lookups on the hub are free with no install or account. As a reference point for scale, our published benchmark measured $1.45 per trusted lead end to end.

It draws on importer and exporter discovery data, WTO and national tariff schedules, the OFAC SDN sanctions list, and live crawls of company websites. Tariff and HS lookups come from official schedules, sanctions checks run against the published SDN data, and buyer discovery and enrichment combine trade records with what the CLI reads from a company's own site. It also reads per-shipment customs and bill-of-lading records, and resolves and verifies decision-maker contacts through people-search and LinkedIn, with web search mapping a raw company name to its canonical site. Every result includes the source it came from, and shipment queries report their own coverage — so your team can trace any row back to where the data originated, see where the data is complete, partial, or unavailable, and decide how far to trust it.

Every contact field comes back as a value paired with its source and a confidence label. Data confirmed by a provider is marked verified; anything the CLI extracted from a website or inferred from other signals is returned as a candidate, not a fact. The labels form a single ladder — verified for provider-confirmed facts, extracted for fields pulled from a website crawl, heuristic for values derived from secondary signals, and inferred for a model's best guess from context — so the gap between a confirmed fact and a hypothesis is always explicit. That separation lets an agent use verified addresses straight away while holding candidates back for a quick human check, so outreach never goes out on a guess. The same value-source-confidence shape is used across enrichment, so confidence reads the same wherever data appears.

Yes. Bulk commands take a list of companies and process them in one run, streaming structured results back as each one resolves instead of forcing one tool call per company. An agent can hand over hundreds of rows, keep working, and read results as they arrive, with each row tagged by company so nothing gets mixed up. When a name is ambiguous, auto-pick resolves the best match, so large lists run without a human disambiguating every entry. Because results stream back tagged by company, you can pipe a bulk discovery straight into enrichment and then staged outreach without re-keying the list, and the run's collections and history stay saved to your account for later sessions. Billable steps still preview before they commit, so you can confirm the scope and cost of a few-hundred-row job before it runs.

Outreach always starts with a dry-run preview that shows exactly what would be sent and to whom. Nothing leaves until you explicitly confirm, and a countdown gives you a final window to cancel before the first message goes out. Once sending begins, replies are tracked per company and the outreach stage is recorded, so an agent can follow up based on where each conversation actually stands rather than re-sending blindly. Sanctions screening runs as an advisory first pass, so you can flag a counterparty before you ever draft a message, while final clearance stays with you and your legal team. Message templates, notes, and per-company stage are kept with each contact, so a sequence picks up exactly where the last touch left off. Opt-outs are honored automatically through a suppression list, so once someone unsubscribes they stay excluded from every later send without you tracking it by hand.

Your collections, saved trade routes, message templates, notes, and per-company history are tied to your authenticated account, not written into your local project files. That keeps prospect lists and negotiation history out of your repo and available across your own sessions instead of leaking into version control. Sign-in is handled through the CLI's own login, so the data stays scoped to you and travels with your account rather than the machine you happen to be on. Because the workspace lives behind your login rather than in the working directory, you can move between machines or hand a task to an agent without copying state around, and nothing you save is shared into another user's account. Sign-in runs through an OAuth device flow rather than a stored password, and the access tokens it issues can be revoked at any time, so account access stays under your control.

Because those are web chats, not agents with access to your machine. The skill file at cli.eximagent.ai/skill is a set of instructions that teaches an AI agent how to run eximagent commands — so the assistant reading it must be able to execute commands in a terminal on your computer. Coding agents like Claude Code, Cursor, Windsurf, and Codex CLI can do exactly that: paste the one-line prompt, and the agent reads the skill, installs the CLI if needed, and drives it for you. A chat website can at best read the file and summarize it — it has no terminal, so nothing runs. If you are in a web chat, the recommended path is the CLI: install it with the one-line command at the top of the page and type commands directly, or hand the skill to a coding agent. The web app at app.eximagent.ai remains available if you prefer not to install anything.