← back

Coresignal vs Openmart

Company Search

Coresignal
Coresignal
85
VS
Openmart
100
Openmart
Metric Coresignal Openmart
Category Company Search Company Search
Pricing Freemium Freemium
Auth API Key API Key
Format JSON JSON
Bot Blocking None None
OpenAPI Spec No Yes
Credit Card Not required Not required
Rate Limit 18 req/s (collect), 54 req/s (bulk POST), 27 req/s (bulk GET) 100 results per request (pagination supported). Plan-specific rate limits — contact Openmart for details.
Score Component Coresignal Openmart
Base +50 +50
OpenAPI Spec 0 (No) +15 (Yes)
Auth +10 (API Key) +10 (API Key)
Format +10 (JSON) +10 (JSON)
Bot Blocking +10 (None) +10 (None)
No CC +5 (Yes) +5 (Yes)
Free 0 (No) 0 (No)
Total 85 100
Coresignal Openmart
Pros
  • + Massive scale — 3B+ records across companies, employees, and jobs with regular freshness updates
  • + Official MCP server for direct LLM/agent integration with multi-source company, employee, and jobs APIs
  • + Clean REST API with simple API key auth, Elasticsearch DSL support for complex queries, and bulk collect endpoints
  • + Rich data per business (40+ fields) — address, phone, email, ratings, hours, decision-maker contacts, tech stack, revenue, and social profiles in a single JSON response
  • + Simple REST API with x-api-key auth and FastAPI-generated OpenAPI spec at /openapi.json — agents can auto-discover endpoints and generate typed clients
  • + Covers local/SMB businesses specifically (30M+ in US/CA/AU), a niche most B2B data providers underserve, making it ideal for agents targeting local business outreach
Cons
  • - No free ongoing tier — free trial is 14 days only, paid plans start at $49/mo with limited credits
  • - Raw data may require preprocessing (duplicates, HTML artifacts, inconsistent formatting from web-scraped sources)
  • - Credit-based pricing across all tiers — agents must track credit consumption, and enriched fields (owner contacts, tech stack) cost more than basic lookups
  • - Batch people-lookup endpoint is async (poll for status), adding complexity for agents that expect synchronous responses
Badges
API KeyFreemiumJSONBot Blocking: NoneNo CCb2b-datacompany-dataemployee-datajob-postingsfirmographicsbulk-queriesmcp-server
OpenAPI SpecAPI KeyFreemiumJSONBot Blocking: NoneNo CClocal-businessbusiness-searchlead-generationdecision-makerstech-stackdata-enrichmentb2b-datagoogle-maps

Coresignal Integration

example.py
import requests
API_KEY = "your-api-key"BASE = "https://api.coresignal.com/cdapi/v2"headers = {"apikey": API_KEY, "accept": "application/json"}
# Collect company by IDresp = requests.get(f"{BASE}/company_base/collect/12345", headers=headers)print(resp.json())
# Search companiesresp = requests.post(f"{BASE}/company_base/search", headers=headers,    json={"name": "Anthropic", "country": "United States"})print(resp.json())

Openmart Integration

example.py
import requests
headers = {    "x-api-key": "YOUR_API_KEY",    "Content-Type": "application/json"}
# Search for local businessesresp = requests.post(    "https://api.openmart.ai/api/v1/search",    headers=headers,    json={        "query": "plumbers",        "location": [{"city": "Los Angeles", "state": "CA"}],        "limit": 100    })businesses = resp.json()for biz in businesses.get("results", []):    print(biz["name"], biz.get("phone"), biz.get("email"))