LeanData website screenshot

LeanData

LeanData is a Sunnyvale, California revenue orchestration platform built on the Salesforce ecosystem. The company is best known for inventing lead-to- account matching and lead routing for B2B revenue teams; its managed package on the Salesforce AppExchange has been deployed by more than 1,000 B2B companies including Uber, Palo Alto Networks, Shopify, Zoom, New Relic, Snowflake, and DocuSign. The current platform spans four product lines β€” Orchestration (lead/contact/account routing, deduplication, SLAs, signal workflows), BookIt (forms, handoff, and links-based scheduling), Buying Groups (multi-stakeholder pipeline and engagement), and Revenue Insights (reporting and analytics). LeanData exposes four developer APIs that wrap the platform's core capabilities β€” the Matching API (real-time lead / contact / account identification from external systems), the Round Robin API (advanced weighted distribution, working hours, and vacation-aware assignment), the BookIt API (scheduling inputs, availability, and meeting CRUD for custom UIs), and the Graph API (one-time routing and routing-graph metadata for custom orchestration). The Matching and Round Robin APIs are Salesforce-native and dispatched through the managed package's Apex REST endpoint at /services/apexrest/LeanData/LeanDataAPI, authenticated with the customer's own Salesforce OAuth 2.0 Connected App; BookIt and Graph are hosted at api.leandata.com behind AWS API Gateway and authenticated with a server-side API key in an X-Api-Key header. Since the Q2 2026 release LeanData also runs a hosted BookIt MCP server at https://mcp.leandata.com/mcp β€” currently labelled beta β€” which exposes BookIt scheduling and operational data to MCP-compatible AI clients under OAuth 2.1 with PKCE and dynamic client registration, with admin, user and partner scopes and tool visibility filtered by the caller's BookIt permission set. Developer documentation is published as a public Postman collection at docs.leandata.com. Commercial offerings are tiered across Standard, Advanced, Premium, and Enterprise editions of Orchestration plus BookIt scheduling products and Buying Groups, with implementation services billed separately.

LeanData publishes 9 APIs on the APIs.io network, including πŸ—“οΈ Availability API, Legacy (still supported) API, Matching API, and 6 more. Tagged areas include Revenue Operations, Lead Routing, Lead to Account Matching, Salesforce, and Sales Engagement.

LeanData’s developer surface includes developer portal, documentation, changelog, pricing, training material, engineering blog, YouTube channel, and 57 more developer resources.

60.7/100 strong ▬ flat Agent 48/100 agent ready Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
AccessPaid
9 APIs 1 MCP Servers
Revenue OperationsLead RoutingLead to Account MatchingSalesforceSales EngagementSales ProductivityMarketing OperationsSchedulingMeeting BookingAccount Based MarketingBuying GroupsSignal OrchestrationGo-To-MarketCRMAppExchange

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 60.7/100 · strong
Contract Quality 11.2 / 25
Developer Ergonomics 11.8 / 20
Access Clarity 20.0 / 20
Operational Transparency 6.5 / 13
Contract Governance 2.0 / 12
Discoverability 9.3 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 6 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts β€” every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/leandata: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling β€” $2,500 →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

LeanData πŸ—“οΈ Availability API

The availability endpoints return meeting configuration and open time slots used to render booking pages or refresh availability. Depending on the request context (routing, d...

LeanData Legacy (still supported) API

This section outlines the endpoints used to retrieve scheduling data for building a custom calendaring experience. Both endpoints return the same structure of read-on...

LeanData Matching API

The Matching API from LeanData β€” 1 operation(s) for matching.

LeanData πŸ“† Meetings > Create API

Use these endpoints to finalize and book meetings after a timeslot has been selected.

⚠️ Important: You must support both POST ...

LeanData πŸ“† Meetings > Manage API

The πŸ“† Meetings > Manage API from LeanData β€” 1 operation(s) for πŸ“† meetings > manage.

LeanData πŸ“† Meetings > Retrieve API

The πŸ“† Meetings > Retrieve API from LeanData β€” 2 operation(s) for πŸ“† meetings > retrieve.

LeanData One Time Routing API

This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience, as well as to retrieve the status of the resulting job. When i...

LeanData Retrieve Routing Graphs Information API

This section outlines the endpoints used to retrieve Routing Graphs information for building a custom orchestration experience. The endpoint returns information such as trigg...

LeanData 🧠 Scheduling Inputs API

The 🧠 Scheduling Inputs API from LeanData β€” 1 operation(s) for 🧠 scheduling inputs.

Scroll for all 9

Open Collections 13

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll for all 13

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

LeanData BookIt MCP (remote, https://mcp.leandata.com/mcp)

LeanData ships a hosted, remote BookIt MCP server, announced in the Q2 2026 release. It exposes BookIt scheduling and operational data to any MCP client (Claude, ChatGPT, Agentf...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Leandata Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Leandata Authentication

apiKey/oauth2 Β· 4 schemes

SECURITY

Leandata Domain Security

TLSv1.3 Β· DMARC

SECURITY

Leandata Trust Center

SOC 2 Type 2, GDPR, CCPA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Leandata Scopes

4 scopes Β· authorizationCode

4 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Leandata Agentic Access

16 operations Β· 12 acting

16 operations · 12 acting

AGENTIC

Resources

Documentation 3

Reference material describing how the API behaves

Learn 3

Tutorials, courses, talks, and written guidance

Source (apis.yml)

apis.yml Raw ↑
aid: leandata
name: LeanData
description: LeanData is a Sunnyvale, California revenue orchestration platform built on the Salesforce ecosystem. The company
  is best known for inventing lead-to- account matching and lead routing for B2B revenue teams; its managed package on the
  Salesforce AppExchange has been deployed by more than 1,000 B2B companies including Uber, Palo Alto Networks, Shopify, Zoom,
  New Relic, Snowflake, and DocuSign. The current platform spans four product lines β€” Orchestration (lead/contact/account
  routing, deduplication, SLAs, signal workflows), BookIt (forms, handoff, and links-based scheduling), Buying Groups (multi-stakeholder
  pipeline and engagement), and Revenue Insights (reporting and analytics). LeanData exposes four developer APIs that wrap
  the platform's core capabilities β€” the Matching API (real-time lead / contact / account identification from external systems),
  the Round Robin API (advanced weighted distribution, working hours, and vacation-aware assignment), the BookIt API (scheduling
  inputs, availability, and meeting CRUD for custom UIs), and the Graph API (one-time routing and routing-graph metadata for
  custom orchestration). The Matching and Round Robin APIs are Salesforce-native and dispatched through the managed package's
  Apex REST endpoint at /services/apexrest/LeanData/LeanDataAPI, authenticated with the customer's own Salesforce OAuth 2.0
  Connected App; BookIt and Graph are hosted at api.leandata.com behind AWS API Gateway and authenticated with a server-side
  API key in an X-Api-Key header. Since the Q2 2026 release LeanData also runs a hosted BookIt MCP server at https://mcp.leandata.com/mcp
  β€” currently labelled beta β€” which exposes BookIt scheduling and operational data to MCP-compatible AI clients under OAuth
  2.1 with PKCE and dynamic client registration, with admin, user and partner scopes and tool visibility filtered by the caller's
  BookIt permission set. Developer documentation is published as a public Postman collection at docs.leandata.com. Commercial
  offerings are tiered across Standard, Advanced, Premium, and Enterprise editions of Orchestration plus BookIt scheduling
  products and Buying Groups, with implementation services billed separately.
tags:
- Revenue Operations
- Lead Routing
- Lead to Account Matching
- Salesforce
- Sales Engagement
- Sales Productivity
- Marketing Operations
- Scheduling
- Meeting Booking
- Account Based Marketing
- Buying Groups
- Signal Orchestration
- Go-To-Market
- CRM
- AppExchange
tags_raw:
- Revenue Operations
- Lead Routing
- Lead to Account Matching
- Salesforce
- Sales Engagement
- Sales Productivity
- Marketing Operations
- Scheduling
- Meeting Booking
- Account Based Marketing
- Buying Groups
- Signal Orchestration
- Go to Market
- RevOps
- GTM
- CRM
- AppExchange
type: Index
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
position: Provider
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/leandata.png
url: https://raw.githubusercontent.com/api-evangelist/leandata/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: leandata:leandata-availability-api
  name: LeanData πŸ—“οΈ Availability API
  description: '<p>The availability endpoints return meeting configuration and open time slots used to render booking pages
    or refresh availability. Depending on the request context (routing, direct link, or reschedule), the response includes
    meeting details, eligible hosts, and available time windows.</p>

    <ul>

    <li><p><strong>POST</strong> <code>/v1/scheduling/route-and-fetch-availability</code></p>

    </li>

    <li><p><strong>POST</strong> <code>/v1/scheduling/fetch-availability</code></p>

    </li>

    </ul>'
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - Availability
  tags_raw:
  - πŸ—“οΈ Availability
  properties:
  - type: OpenAPI
    url: openapi/leandata-availability-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-availability-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-legacy-still-supported-api
  name: LeanData Legacy (still supported) API
  description: '<p>This section outlines the endpoints used to retrieve scheduling data for building a custom calendaring
    experience. Both endpoints return the same structure of <strong>read-only</strong> informationβ€”including scheduling metadata,
    working hours, available time slots, and configured usersβ€”that can be used to render the scheduling page.</p>

    <ul>

    <li><p><strong><code>v1/scheduling/retrieve-info</code></strong> β€” Use this endpoint <strong>when booking a meeting</strong>
    <strong>for the first time</strong>.</p>

    </li>

    <li><p><strong><code>v1/scheduling/retrieve-modification-info</code></strong> β€” Use this endpoint <strong>when modifying
    an existing meeting</strong>, such as rescheduling or canceling.</p>

    </li>

    </ul>

    <p>These endpoints provide all the data needed to power the UI for selecting a meeting time and pre-populating prospect
    details.</p>'
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - Legacy (still supported)
  properties:
  - type: OpenAPI
    url: openapi/leandata-legacy-still-supported-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-legacy-still-supported-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-matching-api
  name: LeanData Matching API
  description: The Matching API from LeanData β€” 1 operation(s) for matching.
  humanURL: https://docs.leandata.com
  baseURL: https://yourinstance.my.salesforce.com
  tags:
  - Matching
  properties:
  - type: OpenAPI
    url: openapi/leandata-matching-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-matching-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-meetings-create-api
  name: LeanData πŸ“† Meetings > Create API
  description: '<p>Use these endpoints to finalize and book meetings after a timeslot has been selected.</p>

    <p>⚠️ <strong>Important:</strong> You <strong>must</strong> support both <code>POST /v1/meeting</code> and <code>POST
    /v1/round-robin-meeting</code>.</p>

    <p>The correct endpoint is determined by the availability response:</p>

    <ul>

    <li><p>If <code>pageInfo.displayAllPoolAvailability = true</code>, you must book using <code>POST /v1/round-robin-meeting</code>.</p>

    </li>

    <li><p>If <code>pageInfo.displayAllPoolAvailability = null</code> or <code>false</code>, you must book using <code>POST
    /v1/meeting</code>.</p>

    </li>

    </ul>

    <p>This behavior is driven by your scheduling graph configuration and cannot be assumed ahead of time.</p>'
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - πŸ“† Meetings > Create
  properties:
  - type: OpenAPI
    url: openapi/leandata-meetings-create-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-meetings-create-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-meetings-manage-api
  name: LeanData πŸ“† Meetings > Manage API
  description: The πŸ“† Meetings > Manage API from LeanData β€” 1 operation(s) for πŸ“† meetings > manage.
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - πŸ“† Meetings > Manage
  properties:
  - type: OpenAPI
    url: openapi/leandata-meetings-manage-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-meetings-manage-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-meetings-retrieve-api
  name: LeanData πŸ“† Meetings > Retrieve API
  description: The πŸ“† Meetings > Retrieve API from LeanData β€” 2 operation(s) for πŸ“† meetings > retrieve.
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - πŸ“† Meetings > Retrieve
  properties:
  - type: OpenAPI
    url: openapi/leandata-meetings-retrieve-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-meetings-retrieve-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-one-time-routing-api
  name: LeanData One Time Routing API
  description: '<p>This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience,
    as well as to retrieve the status of the resulting job. When invoked, the 1x Routing endpoint returns basic job metadataβ€”including
    the <code>jobId</code>β€”which can be used to check the job’s status.</p>

    <ul>

    <li><p><code>orchestration/v1/one-time-routing</code> β€” Use this endpoint to invoke 1x routing for a particular SFDC org</p>

    </li>

    <li><p><code>orchestration/v1/one-time-routing/:jobId</code> β€” Use this endpoint to retrieve the job status of a 1x routing
    for a particular SFDC org</p>

    </li>

    </ul>

    <p>❗️ <strong>Important:</strong> The API does <strong>not</strong> validate FlowBuilder graphs before triggering routing.
    If you invoke 1x Routing to an invalid or misconfigured graph, the request will still be processedβ€”but routing will fail
    silently. No error response will be returned from the API.<br />βœ… To avoid unexpected behavior, please ensure the graph
    is valid and functioning as expected within the LeanData application before using it in API-triggered routing.</p>'
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - One Time Routing
  properties:
  - type: OpenAPI
    url: openapi/leandata-one-time-routing-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-one-time-routing-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-retrieve-routing-graphs-information-api
  name: LeanData Retrieve Routing Graphs Information API
  description: '<p>This section outlines the endpoints used to retrieve Routing Graphs information for building a custom orchestration
    experience. The endpoint returns information such as trigger node names, the edges in those trigger nodes, graph name,
    etc</p>

    <ul>

    <li><code>orchestration/v1/routing-graphs</code> β€” Use this endpoint <strong>when fetching routing graphs</strong> from
    a particular SFDC org.</li>

    </ul>'
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - Retrieve Routing Graphs Information
  properties:
  - type: OpenAPI
    url: openapi/leandata-retrieve-routing-graphs-information-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-routing-graphs-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
- aid: leandata:leandata-scheduling-inputs-api
  name: LeanData 🧠 Scheduling Inputs API
  description: The 🧠 Scheduling Inputs API from LeanData β€” 1 operation(s) for 🧠 scheduling inputs.
  humanURL: https://docs.leandata.com
  baseURL: https://api.leandata.com
  tags:
  - 🧠 Scheduling Inputs
  properties:
  - type: OpenAPI
    url: openapi/leandata-scheduling-inputs-api-openapi.yml
  - type: Overlay
    url: overlays/leandata-scheduling-inputs-overlay.yaml
  - type: Documentation
    url: https://docs.leandata.com
common:
- type: TrustCenter
  url: security/leandata-trust-center.yml
- type: AgenticAccess
  url: agentic-access/leandata-agentic-access.yml
- type: DomainSecurity
  url: security/leandata-domain-security.yml
- type: Website
  url: https://www.leandata.com
- type: Portal
  url: https://docs.leandata.com
  name: LeanData API Documentation
- type: Documentation
  url: https://docs.leandata.com
- type: Documentation
  url: https://api.leandatainc.com
  name: Legacy Matching API Documentation
- type: SupportPortal
  url: https://leandatahelp.zendesk.com
  name: LeanData Help Center
- type: SupportPortal
  url: https://support.leandata.com
  name: LeanData Support
- type: ChangeLog
  url: https://leandatahelp.zendesk.com/hc/en-us/sections/360002566353-Release-Notes
- type: Pricing
  url: https://www.leandata.com/pricing/
- type: Plans
  url: plans/leandata-plans-pricing.yml
- type: RateLimits
  url: rate-limits/leandata-rate-limits.yml
- type: FinOps
  url: finops/leandata-finops.yml
- type: Product
  url: https://www.leandata.com/platform/
  name: LeanData Platform
- type: Product
  url: https://www.leandata.com/platform/orchestration/
  name: Orchestration
- type: Product
  url: https://www.leandata.com/platform/bookit/
  name: BookIt
- type: Product
  url: https://www.leandata.com/platform/buying-groups/
  name: Buying Groups
- type: Integrations
  url: https://www.leandata.com/platform/integrations/
- type: Customers
  url: https://www.leandata.com/customers/
- type: Training
  url: https://www.leandata.com/learning-center/
  name: Learning Center
- type: Training
  url: https://www.leandata.com/certification/
  name: LeanData Certification
- type: Resources
  url: https://www.leandata.com/resources/
- type: Blog
  url: https://www.leandata.com/blog/
- type: Forums
  url: https://www.opsstars.com/
  name: OpsStars Community
- type: AppExchange
  url: https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B4HCREA3
  name: LeanData on Salesforce AppExchange
- type: Company
  url: https://www.leandata.com/company/
- type: Careers
  url: https://www.leandata.com/careers/
- type: Contact
  url: https://www.leandata.com/contact/
- type: Newsroom
  url: https://www.leandata.com/press/
- type: TrustCenter
  url: https://trust.leandata.com/
  name: LeanData Trust Center (SafeBase)
- type: TrustCenter
  url: security/leandata-trust-center.yml
  name: Trust center profile
- type: PrivacyPolicy
  url: https://www.leandata.com/privacy/
- type: TermsOfService
  url: https://www.leandata.com/terms-of-service/
- type: LinkedIn
  url: https://www.linkedin.com/company/leandatainc/
- type: Twitter
  url: https://twitter.com/leandatainc
- type: YouTube
  url: https://www.youtube.com/@leandatainc
- type: GitHubOrganization
  url: https://github.com/leandata
- type: Authentication
  url: authentication/leandata-authentication.yml
  name: X-Api-Key (BookIt, Graph); Salesforce OAuth 2.0 Connected App (Matching, Round Robin); OAuth 2.1 (BookIt MCP)
- type: DeveloperPortal
  url: https://docs.leandata.com
  name: LeanData API Documentation
- type: APIReference
  url: https://docs.leandata.com
  name: LeanData API reference (Postman documenter)
- type: GettingStarted
  url: https://docs.leandata.com
  name: Get Started with the LeanData APIs
- type: Postman
  url: https://www.postman.com/leandata/workspace/leandata-s-public-workspace
  name: LeanData's Public Workspace
- type: Support
  url: https://support.leandata.com
  name: LeanData Support
- type: Login
  url: https://login.leandata.com
  name: LeanData application login
- type: SignUp
  url: https://www.leandata.com/demo-request/
  name: Request a demo (no self-service signup)
- type: MCPServer
  url: mcp/leandata-mcp.yml
  name: LeanData BookIt MCP (remote, https://mcp.leandata.com/mcp)
- type: ToolCrosswalk
  url: mcp/leandata-tool-crosswalk.yml
- type: WellKnown
  url: well-known/leandata-well-known.yml
- type: LLMsTxt
  url: llms/leandata-llms.txt
- type: OAuthScopes
  url: scopes/leandata-scopes.yml
- type: Conventions
  url: conventions/leandata-conventions.yml
- type: ErrorCatalog
  url: errors/leandata-problem-types.yml
- type: DataModel
  url: data-model/leandata-data-model.yml
- type: Lifecycle
  url: lifecycle/leandata-lifecycle.yml
- type: StatusPage
  url: https://status.leandata.com
  name: LeanData Status
- type: ChangeLog
  url: changelog/leandata-changelog.yml
  name: LeanData release history
- type: Conformance
  url: conformance/leandata-conformance.yml
- type: Compliance
  url: https://trust.leandata.com/
  name: SOC 2 Type 2, GDPR, CCPA
- type: VulnerabilityDisclosure
  url: security/leandata-vulnerability-disclosure.yml
- type: Security
  url: https://trust.leandata.com/?itemUid=64c9680b-ef79-4c92-baa0-13b541954bef
  name: Responsible Disclosure
- type: Packages
  url: packages/leandata-packages.yml
- type: Components
  url: components/leandata-components.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/leandata-availability-overlay.yaml
  name: API Evangelist overlays
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 33
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client β€” Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs β€” one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free β€” the basis for a claim should not sit behind it.
  • get_provider_ratingPRO β€” composite, band, trend and facet scores.
  • apis_io_searchSTART HERE β€” APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/leandata"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/leandata/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/leandata/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.