High risk
Done-for-you recommended
HIPAASOC2

Insurance Pre-check Agent

Coverage confirmed before the chair, with fewer billing disputes.

A ready-to-build governance package for Dental Practices. Your runtime enforces it; Agent Bob does not run the agent.

Purpose

You want eligibility and benefits checked before each visit so patients are not surprised at checkout. This agent looks up coverage read-only and flags frequency limits, waiting periods and missing information. Billing staff review any gap or denial before the patient is told.

It will

  • Read-only payer eligibility lookups — no claims submission, pre-authorization requests, or billing code changes

It won't

  • Submit claims or pre-authorizations, quote out-of-pocket estimates directly to patients, store raw payer responses beyond the session

It asks a person first

  • Escalate to the billing manager when frequency limits, waiting periods, or missing-tooth clauses apply
  • Billing staff must review any coverage gap or denial before the patient is notified

Tools

  • Web research
  • Database updates
  • Web research: Look things up online.
  • Database updates: Change records in a database.

✋ Every outbound action needs your approval

Budget defaults

Per task
$0.50
Per month
$60
Actions a day
60

The runtime pauses the agent at a limit. You can change every number in the builder.

Memory and autonomy

No memory. Nothing is kept between runs.

ClawMaven policy: zero retention of payer response data after session ends

Supervised: it prepares the work and a person approves it.

What you get

The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.

  • HANDOFF.md What your runtime has to enforce, file by file
  • agent-blueprint.json The agent's purpose, tools and settings
  • policy.json Hard limits: autonomy, budget, memory, tools, loop bounds
  • trust-manifest.json The integrity manifest your runtime can verify
  • routing.rules.json Which tools need approval before use
  • run-report-template.json What every run reports back
  • approval-gates.md The moments that must pause for a person
  • deployment-checklist.md What to check before it goes live

This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.

Start from this package

Bob pre-fills the builder with it and drafts the rest. You confirm every step.

Build this packageGet it built for you