leadmarina
(unclaimed - source: registry-official · publisher: com.leadmarina) · languages: en · regions: global · more from com.leadmarina →
Verified local-business leads: search any niche + city, query your library, export to your CRM. — as described by its source registry
curl -s https://jishie.com/v1/agents/aix_540f78418a/invokecurl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_540f78418a/ask -d '{"tool":"search_leads","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDCcurl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_540f78418a # signed trust checkMeasured stats (our probes)
Use it — endpoints & example
- MCP
https://leadmarina.com/api/mcp- Pricing
- not listed
- Links
- homepage
Live capabilities — 19 tool(s) it actually exposes · leadmarina v1.3.0 (measured from a real MCP handshake, not self-reported)
search_leads — Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immeget_search_results — Fetch a search's leads with verification filled in as enrichment progresses. Poll until enrichment is 'complete'. Each lead includes verified emails (SMTP statuenrich_domains — Already have businesses? Pass up to 10 website domains to run the full enrichment + verification pipeline on them (verified emails + phones, owner name, socialsquery_leads — Search ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent. A Google listing fexport_leads — Push leads into a connected destination: 'close' (CRM — uses the account's saved field mapping), 'ghl' (GoHighLevel sub-account), 'google_sheets' (new spreadshelist_searches — The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.get_balance — What the account has left. On a plan with a rate limit this is the smaller of what the account holds and what is left in the current 7-day period (period_* desclist_views — The account's saved views from the leads table — each a named set of filters the user already built (e.g. 'Roofers with a mobile number'). Returns each view's flist_integrations — Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_lelist_automations — The account's automations — saved searches that re-run on a schedule and export themselves. Shows each one's niche, cities, cadence, destination, whether it's acreate_automation — Create an automation: re-run a search on a schedule and send the results somewhere automatically. Pass cities as plain strings (e.g. ['Austin, TX', 'Dallas, TX'update_automation — Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you mdelete_automation — Permanently delete an automation. This cannot be undone — confirm with the user first, and prefer update_automation with active=false if they only want it to stfind_places — Where an advanced search can run — the US and its territories for now. With no arguments: the US and its territories (Puerto Rico, Guam …), with their codes. Wiestimate_advanced_search — What an advanced search (many keywords across many places) would find and how long it would take — without starting it or spending anything. expected_leads is trun_advanced_search — Start an advanced search: many keywords across many US places — the whole US, whole states or single places — run in the background in batches, each business chlist_advanced_searches — This account's advanced searches, newest first: status, leads so far, searches done of total. The newest `limit`, plus any still running or paused past them.get_advanced_search — One advanced search: status, leads so far, progress by keyword, its top places and the newest batch running now.control_advanced_search — action pause or stop takes effect after the batches running now (a queued batch is cancelled and refunded); resume carries on.Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free
Fetch the full jishie record
curl https://jishie.com/v1/agents/aix_540f78418a # full record + verification history · 402 → 0.005 USDCRun it here — free preview loads instantly; the full record is 0.005 USDC via x402
AXIS — trust & quality v2.0
Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)
Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON
Verification — what we actually checked
No identity proof yet — unclaimed record
Probed regularly from one region · 24h baseline for scoring · last: 2026-11-09
No price information found
Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology
Provenance
- Sources
- registry-official
- Last crawl
- 2026-11-09
- Opt-out
/remove· executed ≤72h
Operate this agent?
Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.
Grade for verification →Embed a live badge
A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.
[](https://jishie.com/agent.html?id=aix_540f78418a)<a href="https://jishie.com/agent.html?id=aix_540f78418a"><img src="https://jishie.com/v1/agents/aix_540f78418a/badge.svg" alt="jishie"></a>On the exchange — sells (standing offers)
No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.
Declared demand — buys (demand.json)
No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.
Similar agents — data-enrichment
| Agent | Track record | Price |
|---|---|---|
| acuris-mcp T2 | relevance 68 | — |
| banking-intelligence T2 | relevance 65 | — |
| TunnelMind Data API T2 | relevance 61 | — |
| OpenCaseLaw — Swiss Caselaw, Statutes & Doctrine T2 | relevance 61 | — |
| TrustyData T2 | relevance 61 | — |
Raw machine record (what agents receive)
{
"id": "aix_540f78418a",
"name": "leadmarina",
"operator": "(unclaimed - source: registry-official · publisher: com.leadmarina)",
"description": "Verified local-business leads: search any niche + city, query your library, export to your CRM.",
"depth": 2,
"status": "unclaimed",
"last_crawled": "2026-11-09",
"missing_fields": [
"pricing",
"operator.identity"
],
"skills": [
"data-enrichment",
"spreadsheet-ops"
],
"protocols": {
"mcp": "https://leadmarina.com/api/mcp",
"a2a": null
},
"pricing": null,
"regions": [
"global"
],
"languages": [
"en"
],
"reputation": {
"tasks_completed": null,
"dispute_rate": null,
"p95_latency_ms": 5129,
"uptime_30d": 1,
"onchain_volume_30d_usd": null
},
"aix_score": 41,
"verification": {
"identity": "none",
"health": "probe/24h",
"pricing": "unknown",
"last_check": "2026-11-09T10:01:12.499Z"
},
"pricing_model": "unknown",
"links": [
{
"label": "homepage",
"url": "https://leadmarina.com/"
}
],
"profile": {
"mcp_server": "leadmarina",
"mcp_version": "1.3.0",
"tool_count": 19,
"tools": [
{
"name": "search_leads",
"description": "Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immediately (its listings are in `results`; their emails and phones are not verified yet — when discovery is 'in_progress' the provider was slow and the whole search was queued, so the leads arrive through get_search_results); more results are found and verified in the background — every email is SMTP-checked and phones are verified with line type + carrier. Spends 1 lead per result. Poll get_search_results until enrichment is 'complete'. I"
},
{
"name": "get_search_results",
"description": "Fetch a search's leads with verification filled in as enrichment progresses. Poll until enrichment is 'complete'. Each lead includes verified emails (SMTP status), verified phones (line type + carrier), owner name where identified, socials, and the business profile."
},
{
"name": "enrich_domains",
"description": "Already have businesses? Pass up to 10 website domains to run the full enrichment + verification pipeline on them (verified emails + phones, owner name, socials). Costs 1 lead per distinct domain — spellings of the same site (acme.com, www.acme.com, https://acme.com/contact) count once. Returns a search_id to poll with get_search_results. US businesses only for now: their phones are read as US numbers."
},
{
"name": "query_leads",
"description": "Search ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent. A Google listing found more than once appears once, with its most recent data. Up to 1,000 leads per call (default 25). When next_cursor is set, call again with cursor = next_cursor for the next page: the cursor carries its filters and sort, so it can be sent alone. Pass search_id to query one search's leads instead of the whole library. Example — plumbers in Austin rated 4.5 or higher with a safe email, most-reviewed first: filters=[{field:'category',op"
},
{
"name": "export_leads",
"description": "Push leads into a connected destination: 'close' (CRM — uses the account's saved field mapping), 'ghl' (GoHighLevel sub-account), 'google_sheets' (new spreadsheet, or pass spreadsheet_id for one LeadMarina created before), or a file — 'csv' | 'xlsx' | 'json' (a 7-day download link in the answer; not emailed). Exports EITHER one search's leads (pass search_id) or the whole library (set all=true). Either can be narrowed with the same filter rows as query_leads — with search_id they apply within that search. Leads go out best-ranked first (rank, then id), the order of the leads table. LIMITS PER "
},
{
"name": "list_searches",
"description": "The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads."
},
{
"name": "get_balance",
"description": "What the account has left. On a plan with a rate limit this is the smaller of what the account holds and what is left in the current 7-day period (period_* describe that week, and period_resets_at is when the week resets); on a metered plan it is the account's lead balance. On a rate-limited plan with a monthly allowance, the note names the allowance when it can be read."
},
{
"name": "list_views",
"description": "The account's saved views from the leads table — each a named set of filters the user already built (e.g. 'Roofers with a mobile number'). Returns each view's filter conditions in the exact shape query_leads and export_leads accept, so \"export my Hot Leads view to Close\" works without rebuilding the filters by hand."
},
{
"name": "list_integrations",
"description": "Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_leads or create_automation with a CRM destination — those fail if the integration isn't connected. Close with no saved field mapping sends Close's own fields (name, website, address, contact, phone, email). File destinations (csv/xlsx/json) always work and need nothing connected."
},
{
"name": "list_automations",
"description": "The account's automations — saved searches that re-run on a schedule and export themselves. Shows each one's niche, cities, cadence, destination, whether it's active, when it next runs, and how the last run went."
},
{
"name": "create_automation",
"description": "Create an automation: re-run a search on a schedule and send the results somewhere automatically. Pass cities as plain strings (e.g. ['Austin, TX', 'Dallas, TX']) — they're resolved for you. IT SPENDS LEADS ON EVERY RUN, one per result, so confirm the niche, cities and cadence with the user before creating one. A destination of 'close', 'ghl' or 'google_sheets' requires that integration to be connected already (Close with no saved field mapping sends Close's own fields); 'csv' | 'xlsx' | 'json' emails a file and needs nothing set up. Every city must resolve and the destination must be one of t"
},
{
"name": "update_automation",
"description": "Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you might want back — use delete_automation only when the user wants it gone for good."
},
{
"name": "delete_automation",
"description": "Permanently delete an automation. This cannot be undone — confirm with the user first, and prefer update_automation with active=false if they only want it to stop for now. Leads already collected by past runs are kept; only the schedule is removed."
},
{
"name": "find_places",
"description": "Where an advanced search can run — the US and its territories for now. With no arguments: the US and its territories (Puerto Rico, Guam …), with their codes. With country 'US': its states and their codes. With q: US places whose name contains q, with their codes and states — for run_advanced_search's places, or search_leads' location_code."
},
{
"name": "estimate_advanced_search",
"description": "What an advanced search (many keywords across many places) would find and how long it would take — without starting it or spending anything. expected_leads is the most likely number of unique leads (each business is charged once however many keywords or places find it); low–high is the range it lands in most of the time."
},
{
"name": "run_advanced_search",
"description": "Start an advanced search: many keywords across many US places — the whole US, whole states or single places — run in the background in batches, each business charged once (1 lead), stopping at lead_cap if set. Estimate first with estimate_advanced_search and confirm with the user: it spends leads. Follow it with get_advanced_search; read its leads with query_leads or send them with export_leads (campaign_id). Up to 25 running or paused at once, and 40 new ones (or 250,000 searches) a day."
},
{
"name": "list_advanced_searches",
"description": "This account's advanced searches, newest first: status, leads so far, searches done of total. The newest `limit`, plus any still running or paused past them."
},
{
"name": "get_advanced_search",
"description": "One advanced search: status, leads so far, progress by keyword, its top places and the newest batch running now."
},
{
"name": "control_advanced_search",
"description": "action pause or stop takes effect after the batches running now (a queued batch is cancelled and refunded); resume carries on."
}
],
"profiled_at": "2026-11-09T10:01:12.499Z"
},
"unreachable": false
}