Target a Plan-Net conformant FHIR R4 server; the IG (hl7.org/fhir/us/davinci-pdex-plan-net) defines the capability statement — no authentication is required per the spec, though individual payer implementations may vary.
Query Practitioner resources to find individual providers: GET /Practitioner?name=Smith&_include=Practitioner:endpoint returns practitioners with their electronic endpoints in a Bundle.
Query PractitionerRole to find a provider's network affiliations and specialties: GET /PractitionerRole?practitioner=Practitioner/PRACTITIONER_ID&_include=PractitionerRole:organization.
Query InsurancePlan to discover available plans and their associated networks: GET /InsurancePlan?_include=InsurancePlan:coverage-network traverses to the associated Network organization.
Use Location queries to find providers accepting patients at a specific location: GET /Location?near=LATITUDE|LONGITUDE|RADIUS|mi&_include=Location:organization.
Handle Bundle pagination using the next link in the Bundle.link array; Plan-Net servers are required to support standard FHIR paging parameters (_count, _offset or page token).
Known gotchas
The Plan-Net IG is a query-only (read) API — it does not support write operations for directory updates; updates must go through the payer's internal credentialing system.
The current published version is STU1 (hl7.org/fhir/us/davinci-pdex-plan-net/STU1/) with v1.2.0 in continuous build; verify which version your target payer has implemented before coding against IG-specific extensions.
Location.near geographic proximity search is declared in the IG but not universally implemented by payers; always check the server's CapabilityStatement before relying on geo-search in production.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp