Payer Api Directory

com.dropwatchhqPublished by dropwatchhq.comOfficial publisherv1.0.0Updated Oct 24, 2026

Directory of US clearinghouse/payer APIs (Availity, Optum, Waystar) with pricing & access signals.

The publisher's own server: Agent Receipts

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant browse a directory of US medical clearinghouse and payer API vendors, compare functions and pricing signals, and get ranked recommendations.

What you can do
Provides a directory of US medical clearinghouse and payer API vendors, listing each vendor's access model, API style, supported X12 functions and whether pricing is public. It returns a full record for one vendor, including dated and confidence-tagged pricing signals, access requirements and small-practice fit. It can also filter vendors by X12 function and produce a scored, reasoned shortlist from the functions needed, a dev-integration flag and a budget-sensitive flag.
When to use it
Use it when comparing US clearinghouse or payer API vendors, checking which vendors support a given X12 function, or getting a shortlist ranked against a practice's needs and budget sensitivity.
Requirements
Remote HTTP endpoint; no local runtime needed. The input declares no accounts, API keys, environment variables or headers.

Installation

In SourceWeft

  1. Open Payer Api Directory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.dropwatchhq%2Fpayer-api-directory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "payer-api-directory": {
      "type": "http",
      "url": "https://clearinghouse.dropwatchhq.com/mcp"
    }
  }
}

Tools

4

list_clearinghouses

List all medical clearinghouse / payer-API vendors in the directory with their access model, API style, supported X12 functions, and whether pricing is public.

Takes no parameters.

get_clearinghouse

Full record for one vendor: what it does, dated+confidence-tagged pricing signals, access requirements, and small-practice fit. confidence is one of published/reported/none.

Parametersslugrequired

vendors_by_function

Which vendors support a given X12 function. function slug one of: eligibility, claims, era, claim-status, prior-auth.

Parametersfunctionrequired

recommend_clearinghouse

Transparently rank vendors for a practice. Returns scored shortlist with the reasoning for each. Inputs: functions needed, dev-integration flag, budget-sensitive flag.

ParametersfunctionsdevIntegrationbudgetSensitive

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Dropwatchhq integrations