# Daybook Health

> Daybook Health is centralized infrastructure for healthcare billing: one API in front of every clearinghouse, EHR and payer portal that routes each claim, checks its status, enriches the answer and posts the remit (payer calls, portals, eligibility, ERA enrollment, denials and appeals included), with signed webhooks that bring each answer back and the same operations as MCP tools for AI agents. It is run for the medical billing companies, EHR and practice management vendors and dental billing teams that own the practice relationship, from the systems they already use. Agents do the payer work, and the customer's own team keeps every billing decision. A forward-deployed engineer can wire Daybook into a customer's systems and build the write-back. Pricing is usage-based. No subscriptions and no seats. Customers pay only for what Daybook processes. Daybook does not run a billing company and will not compete with the RCM companies it works with. Nothing is offshored, so there is none of the data-handling, quality or compliance exposure of large offshore teams.

**Not to be confused with daybookhealth.com.** Daybook Health, at daybookhealthcare.com, builds and runs billing agents for medical billing companies, EHR and practice management vendors and dental billing teams. It is a separate company from the AI agent evaluation business at daybookhealth.com, which shares the name, and the two have no affiliation, founders or products in common.

**For medical billers.** Agents that ask every payer for claim status, balance and match every remit, track ERA enrollment for every client and draft appeals, with fewer hands and lower cost than a staffed team. Billers make every call on appeals, write-offs and posting.

**For EHR and practice management vendors.** Agents that run inside the vendor's product for every practice on the platform: claim status with every payer, remits balanced and matched, ERA and EFT enrollment tracked, and underpayment detection that re-adjudicates every paid claim against the practice's payer contract and drafts the appeal. Every answer is written back onto the claim inside the EHR, and the practice's team makes every call.

**For dental billers.** Agents and software that work alongside the practice management system each dental office runs. They read the benefits breakdown before the visit, check the claim and its attachments before it leaves, ask the payer where it is, balance every remit and write back to Open Dental, Dentrix, Eaglesoft, Curve, Denticon, Sensei and tab32. Billers make every call on claims, appeals and posting.

Each page is complete in its HTML, with no JavaScript needed to read it.

## Pages

- [Home](https://daybookhealthcare.com/): what Daybook Health does, with a link to the page for each audience and the newest articles.
- [Articles](https://daybookhealthcare.com/articles): guides for medical billers, EHR teams, dental billing and practices.
- [For medical billers](https://daybookhealthcare.com/billers): agents and software for billing companies.
- [For EHRs](https://daybookhealthcare.com/ehr): revenue cycle agents that EHR and practice management vendors run inside their products.
- [For dental billers](https://daybookhealthcare.com/dental): agents and software for dental billing companies and the billing offices of dental groups.
- [Developer docs](https://daybookhealthcare.com/docs): the API, webhooks and MCP server, workflow by workflow, with the API reference.
- [Ease Health customer story](https://daybookhealthcare.com/customers/ease-health): how Ease Health automated ERA enrollment for the practices it bills for.
- [About](https://daybookhealthcare.com/about): who Daybook Health is, how it works and who it works with.
- [Careers](https://daybookhealthcare.com/careers): jobs at Daybook Health.
- [Pricing](https://daybookhealthcare.com/pricing): how Daybook charges (usage-based, no subscriptions, no seats, no setup fee) and a short quiz that ends in a call with the team; no rates are published.
- [Security](https://daybookhealthcare.com/security): how Daybook protects customer data today.
- [Support](https://daybookhealthcare.com/support): how to reach the Daybook team for help, by email.
- [Privacy Policy](https://daybookhealthcare.com/privacy): what Daybook collects through the website and the product, and who helps handle it (a draft pending review by counsel).
- [Terms of Service](https://daybookhealthcare.com/terms): the terms that govern use of the website and its booking and contact features.

## Solutions by workflow

- [Payer calls](https://daybookhealthcare.com/payer-calls): Daybook calls the payer, works the phone tree, waits on hold and brings back a structured answer, for medical and dental billers.
- [Payer portals](https://daybookhealthcare.com/payer-portals): Daybook signs in to payer portals, MFA included, runs a defined set of steps and reads the result back as data; any change waits for approval.
- [ERA and EFT enrollment](https://daybookhealthcare.com/era-eft-enrollment): every provider enrolled with every payer for electronic remits and payments, tracked to approval, with each signature or letter routed to the person who owns it.
- [Eligibility and benefits](https://daybookhealthcare.com/eligibility-and-benefits): coverage and benefits over 270/271 as plain fields, in real time or in batches, with rechecks on open claims and the dental benefits breakdown before the visit.
- [Claim status](https://daybookhealthcare.com/claim-status): a 276 for every unpaid claim with no portal login, the 277 answer on the claim in plain words with the next step, started by your own rules.
- [Claim status enrichment](https://daybookhealthcare.com/claim-status-enrichment): the richer claim status that answers what a 277 leaves out, fetched through Availity or the payer's portal on request or by rule, as fields on the claim and a signed webhook; an optional line priced per enriched claim.
- [Remittance and posting](https://daybookhealthcare.com/remittance-and-posting): every 835 matched to its claims and its deposit and proven to the cent, with the posting lines proposed and nothing posted without a click.
- [Denials and appeals](https://daybookhealthcare.com/denials-and-appeals): CARC and RARC codes read, every denial sorted by cause with its next step and deadline, and the appeal drafted for billers to approve.

## Docs

The developer docs, page by page. Each page is also Markdown at its URL plus .md (https://daybookhealthcare.com/docs/quickstart.md); every page together is https://daybookhealthcare.com/llms-full.txt, and the OpenAPI spec is https://daybookhealthcare.com/docs/openapi.json.

- [Daybook docs – healthcare billing API, webhooks and MCP](https://daybookhealthcare.com/docs): APIs and webhooks that plug payer calls, portal work, clearinghouse transactions, remits and denials into the systems you already run.
- [Quickstart](https://daybookhealthcare.com/docs/quickstart): Make your first Daybook API request and receive your first webhook: check a claim's status over 276/277 and get the answer back in your own system.
- [Accounts](https://daybookhealthcare.com/docs/accounts): Daybook's sandbox accounts on Stedi's test payers and production accounts for real payers, how to get one, and signing in with Google or an email link.
- [Forward-deployed engineering](https://daybookhealthcare.com/docs/forward-deployed-engineering): How a Daybook forward-deployed engineer wires the API into your PM system, builds the write-back and builds missing screens on the same public API.
- [How Daybook fits your stack](https://daybookhealthcare.com/docs/how-daybook-fits): Where Daybook sits between your PM system, your clearinghouse and the payer, what stays in your systems, and how the API, webhooks and MCP connect them.
- [Authentication](https://daybookhealthcare.com/docs/authentication): How to authenticate to the Daybook API: bearer API keys for sandbox and production accounts, and keeping keys safe, for every endpoint you call.
- [Worklists and rules](https://daybookhealthcare.com/docs/worklists-and-rules): Send Daybook the accounts you already work as a worklist, and write the rules that decide what runs on each one, such as re-checking quiet claims.
- [Idempotency and errors](https://daybookhealthcare.com/docs/idempotency-and-errors): Retry Daybook API requests safely with idempotency keys, and read every error the same way, whichever payer workflow endpoint returned it.
- [API reference](https://daybookhealthcare.com/docs/api-reference): The Daybook REST API reference: every endpoint for payer calls, portals, eligibility, claim status, remits, enrollment and denials, with examples.
- [Webhooks](https://daybookhealthcare.com/docs/webhooks): How Daybook webhooks work: signed events posted to the HTTPS endpoints you register, the event envelope, and a log of every delivery.
- [Webhook event types](https://daybookhealthcare.com/docs/webhooks/event-types): The webhook events Daybook sends and the data each one carries, starting with webhook.test, the signed test event you send from the app or the API.
- [Verifying webhook signatures](https://daybookhealthcare.com/docs/webhooks/verifying-signatures): Check that every Daybook webhook came from Daybook and was not replayed, with signature verification examples in Node, Python and Rust.
- [Webhook deliveries and testing](https://daybookhealthcare.com/docs/webhooks/deliveries): The delivery log Daybook keeps for each webhook endpoint, what counts as a failed delivery, and how to send a signed test event to check your handler.
- [MCP server for healthcare billing agents](https://daybookhealthcare.com/docs/mcp): Give Claude, Cursor or your own AI agents Daybook as MCP tools: claims, payer calls, denials and remits, with the same permissions and audit trail as the app.
- [Connect an MCP client](https://daybookhealthcare.com/docs/mcp/connect): Add Daybook's MCP server to Claude, Claude Desktop, Claude Code, Cursor, VS Code or the Claude Agent SDK, with an assistant token that acts as you.
- [MCP tools](https://daybookhealthcare.com/docs/mcp/tools): Every tool on Daybook's MCP server by area, from the worklist and claims to payer calls, eligibility, denials and remits, with its API equivalent.
- [MCP playbooks](https://daybookhealthcare.com/docs/mcp/playbooks): Ready-made prompts on Daybook's MCP server: work a denial, chase a flagged payment, post a remittance, check a claim and plan a shift.
- [Payer calls from Claude](https://daybookhealthcare.com/docs/mcp/payer-calls): Connect Daybook's voice agent to Claude: start a payer call from a chat, read the answer, reference number and transcript, and record it on the claim.
- [AI agent permissions and safety](https://daybookhealthcare.com/docs/mcp/permissions): What an AI agent connected to Daybook can see and do, what it never sees, what waits for a person, and how its work is recorded and revoked.
- [Build with AI](https://daybookhealthcare.com/docs/mcp/build-with-ai): Daybook's docs for your AI assistant: every page as Markdown, llms.txt, Copy page and Ask AI, the OpenAPI spec, and use case prompts.
- [API workflows](https://daybookhealthcare.com/docs/workflows): Find the Daybook APIs and webhook events you need by workflow: reaching payers, getting providers set up, and following a claim until it is paid.
- [Payer calls API](https://daybookhealthcare.com/docs/workflows/payer-calls): Integrate payer phone calls with the Daybook API: start a call from your queue with your ids, follow its lifecycle, and get the structured answer by webhook.
- [Payer portals API](https://daybookhealthcare.com/docs/workflows/payer-portals): Automate payer portal work with the Daybook API: sign in, run a defined set of steps and read the result back, with an approval where you want one.
- [ERA and EFT enrollment API](https://daybookhealthcare.com/docs/workflows/enrollment): Enroll every provider with every payer for ERA and EFT with one request each, and track every enrollment to approval through Daybook's webhooks.
- [Eligibility API (270/271)](https://daybookhealthcare.com/docs/workflows/eligibility): Check insurance eligibility and benefits over 270/271 with the Daybook API, in real time or by the thousand, and hear when a patient's coverage changes.
- [Claim status API (276/277)](https://daybookhealthcare.com/docs/workflows/claim-status): Run 276/277 claim status checks with the Daybook API in real time and at volume, started by your own rules, and hear back only when a status moves.
- [Remittance and posting API (835)](https://daybookhealthcare.com/docs/workflows/remittance): Pull 835 remits with the Daybook API, match them to their claims and deposits, and approve the proposed posting entries before your write-back runs.
- [Denials and appeals API](https://daybookhealthcare.com/docs/workflows/denials-and-appeals): Read CARC and RARC codes with the Daybook API, sort every denial by cause with its next step and deadline, and draft the appeal letter in one call.
- [Use cases](https://daybookhealthcare.com/docs/use-cases): What teams build on the Daybook API, from denial call queues to 835 posting, each with its endpoints, its steps and a prompt for Claude, ChatGPT or Cursor.
- [Start a payer call](https://daybookhealthcare.com/docs/api-reference/calls/create): POST /v1/calls starts a payer call. Daybook works the phone tree, waits on hold and returns a structured answer.
- [Retrieve a payer call](https://daybookhealthcare.com/docs/api-reference/calls/get): GET /v1/calls/{id}: fetch a payer call, its status and its structured answer once it completes.
- [List payer calls](https://daybookhealthcare.com/docs/api-reference/calls/list): GET /v1/calls: list payer calls by claim, status, payer, time window or your own metadata, newest first.
- [Cancel a payer call](https://daybookhealthcare.com/docs/api-reference/calls/cancel): POST /v1/calls/{id}/cancel: stop a payer call before it dials, end a live one, or stop a repeating series.
- [Tell the agent something on a live payer call](https://daybookhealthcare.com/docs/api-reference/calls/instruct): POST /v1/calls/{id}/instruct: send Daybook's voice agent a note while a payer call is live. Never spoken aloud.
- [Read a payer call transcript](https://daybookhealthcare.com/docs/api-reference/calls/transcript): GET /v1/calls/{id}/transcript: read a payer call turn by turn, with the speaker and timing of each line.
- [Start a payer portal task](https://daybookhealthcare.com/docs/api-reference/portal-tasks/create): POST /v1/portal-tasks has Daybook sign in to a payer portal, run a defined set of steps and read the result back. Part of the payer portals workflow.
- [Retrieve a portal task](https://daybookhealthcare.com/docs/api-reference/portal-tasks/get): GET /v1/portal-tasks/{id} fetches a payer portal task with its pending action and its result, once it has one. Part of the payer portals workflow.
- [Approve a portal action](https://daybookhealthcare.com/docs/api-reference/portal-tasks/approve): POST /v1/portal-tasks/{id}/approve lets a held payer portal action go through, or rejects it, while it waits for approval. Part of the portals workflow.
- [Submit an ERA or EFT enrollment](https://daybookhealthcare.com/docs/api-reference/enrollments/create): POST /v1/enrollments enrolls a provider with a payer for electronic remits (ERA), electronic payments (EFT) or both. Part of the enrollment workflow.
- [Retrieve an enrollment](https://daybookhealthcare.com/docs/api-reference/enrollments/get): GET /v1/enrollments/{id} fetches an ERA or EFT enrollment, its status and whatever the payer is waiting on. Part of the ERA and EFT enrollment workflow.
- [Check eligibility (270/271)](https://daybookhealthcare.com/docs/api-reference/eligibility/create-check): POST /v1/eligibility/checks runs a real-time 270/271 eligibility and benefits check with the payer. Part of the eligibility and benefits workflow.
- [Create a claim status check (276/277)](https://daybookhealthcare.com/docs/api-reference/claim-status/create-check): POST /v1/claim-status/checks runs a real-time 276/277 claim status check with the payer, one claim at a time or in batches. Part of claim status.
- [List 835 remits](https://daybookhealthcare.com/docs/api-reference/remits/list): GET /v1/remits lists the 835 remits Daybook has pulled for you, newest first, ready to match and post. Part of the remittance and posting workflow.
- [Retrieve a remit](https://daybookhealthcare.com/docs/api-reference/remits/get): GET /v1/remits/{id} fetches an 835 remit with its claim lines, its deposit match and the proposed posting. Part of the remittance and posting workflow.
- [Approve a posting](https://daybookhealthcare.com/docs/api-reference/remits/approve-posting): POST /v1/remits/{id}/posting/approve approves or rejects a remit's proposed posting and fires posting.approved for your write-back to pick up.
- [Retrieve a denial](https://daybookhealthcare.com/docs/api-reference/denials/get): GET /v1/denials/{id} fetches a denial with its codes, the cause Daybook sorted it into and the recommended next step. Part of denials and appeals.
- [Draft an appeal](https://daybookhealthcare.com/docs/api-reference/appeals/create): POST /v1/appeals drafts an appeal letter from a denial's data, for a biller to review and send to the payer. Part of the denials and appeals workflow.
- [Create a worklist](https://daybookhealthcare.com/docs/api-reference/worklists/create): POST /v1/worklists sends Daybook the accounts you already work; it runs each item through your rules and reports back per item, by API and webhook.
- [Create a rule](https://daybookhealthcare.com/docs/api-reference/rules/create): POST /v1/rules tells Daybook what to do when something happens, such as re-checking a claim with no answer: one rule, applied to every account.
- [Create a webhook endpoint](https://daybookhealthcare.com/docs/api-reference/webhook-endpoints/create): POST /v1/webhook-endpoints registers an HTTPS URL to receive Daybook's signed webhook events for the workflows and event types you choose.
- [List webhook endpoints](https://daybookhealthcare.com/docs/api-reference/webhook-endpoints/list): GET /v1/webhook-endpoints lists the HTTPS endpoints you have registered to receive Daybook's signed webhook events, across every workflow you use.
- [Delete a webhook endpoint](https://daybookhealthcare.com/docs/api-reference/webhook-endpoints/delete): DELETE /v1/webhook-endpoints/{id} removes a webhook endpoint, so Daybook stops sending events to it. Register its replacement first.
- [Send a test webhook event](https://daybookhealthcare.com/docs/api-reference/webhook-endpoints/test): POST /v1/webhook-endpoints/{id}/test sends one signed webhook.test event to an endpoint now and records the delivery, so you can check your handler.

## Buyer guides

- [Solutions](https://daybookhealthcare.com/solutions): what Daybook's agents do for each team it works with, one page per job.
  - [Claim status automation for billing companies](https://daybookhealthcare.com/solutions/claim-status-automation-for-billing-companies): a 276 for every unpaid claim overnight and the 277 answer on the claim by morning, for every client a billing company runs.
  - [AI claim status for dental offices](https://daybookhealthcare.com/solutions/ai-claim-status-for-dental-offices): agents check every unpaid dental claim overnight and write the answer back to Open Dental, Dentrix or Eaglesoft.
  - [ERA enrollment service for billing companies](https://daybookhealthcare.com/solutions/era-enrollment-service-for-billing-companies): ERA and EFT enrollment tracked payer by payer for every provider, across clients.
  - [Underpayment detection software](https://daybookhealthcare.com/solutions/underpayment-detection-software): every paid claim re-adjudicated against the payer contract, with the appeal drafted, for billing companies and EHR vendors.
  - [Revenue cycle agents for EHR vendors](https://daybookhealthcare.com/solutions/revenue-cycle-agents-for-ehr-vendors): ERA enrollment, remit posting, claim status and underpayments inside an EHR or practice management product, under its name.
  - [AI medical billing software](https://daybookhealthcare.com/solutions/ai-medical-billing-software): agents for billing companies that check claim status, call payers, balance remits, track ERA enrollment and flag underpayments in the systems they already use.
  - [Revenue cycle management software](https://daybookhealthcare.com/solutions/revenue-cycle-management-software): RCM automation for billing companies: claim status, payer calls, remits, ERA enrollment and appeals, on their clients' own PM systems.
  - [Eligibility verification software](https://daybookhealthcare.com/solutions/eligibility-verification-software): real-time 270/271 eligibility checks in plain words for billing companies, with rechecks on open claims and a work item when coverage is not active.
  - [Denial management software](https://daybookhealthcare.com/solutions/denial-management-software): every denial found, its cause and deadline on the claim and the appeal drafted for the billing company's billers to approve.
  - [Dental insurance verification software](https://daybookhealthcare.com/solutions/dental-insurance-verification-software): dental coverage and benefits checked before the visit over 270/271, portals and payer calls, for dental billing companies and DSO billing offices.
- [Compare](https://daybookhealthcare.com/compare): claims automation software and services side by side, with prices, limits and who each one fits.
  - [Best AI medical billing software for billing companies](https://daybookhealthcare.com/compare/best-ai-medical-billing-software-for-billing-companies): tools compared on claim status, remits, ERA enrollment, payer calls and pricing models.
  - [Best dental claims automation software](https://daybookhealthcare.com/compare/best-dental-claims-automation-software): tools for offices, DSOs and billing companies compared on claim status, remits, PMS write-back and pricing.
  - [Daybook vs offshore AR follow-up teams](https://daybookhealthcare.com/compare/daybook-vs-offshore-ar-follow-up): offshore AR follow-up against agents plus a US team: sourced offshore rates, HIPAA and Medicare Advantage offshore rules, and where offshore still fits best.
  - [SuperDial vs Infinitus](https://daybookhealthcare.com/compare/superdial-vs-infinitus): who each AI payer call company serves, what it covers, how it prices, and Daybook as a third option for billing companies.
- [Alternatives](https://daybookhealthcare.com/alternatives): the tools billing teams look at for claim status, payer calls and remits, and where each one fits.
  - [Foji alternatives](https://daybookhealthcare.com/alternatives/foji-alternatives): Overjet Ivy, Pearl, Zentist, Lassie, Vyne, eAssist and Daybook compared on who each fits, PM systems, pricing and where Foji still wins.
  - [SuperDial alternatives](https://daybookhealthcare.com/alternatives/superdial-alternatives): Infinitus, Daybook, offshore AR teams and voice AI platforms compared on who each fits, the work covered and how pricing works.
  - [Infinitus alternatives](https://daybookhealthcare.com/alternatives/infinitus-alternatives): payer-call AI compared on who each is for, the work it covers, how it is priced, and when Infinitus is still the better fit.
  - [Zentist alternatives](https://daybookhealthcare.com/alternatives/zentist-alternatives): Foji, Daybook, eAssist, Pearl, Vyne and Lassie compared for DSOs and dental groups on work covered, PMS write-back, pricing and limits.