Current release boundary
The public experience is a local preview. Private staging has made controlled real-model calls with synthetic data. Public production signup, live customer payments, and patient-data access are not enabled. The model library includes candidates as well as tested models.
Your integration checklist
- Use server-side secrets and narrow model permissions.
- Implement bounded concurrency, idempotency, and handling for uncertain outcomes.
- Exclude prompts, responses, and patient identifiers from operational logs.
- Validate outputs for your application’s task and risk level.
- Verify your workspace and route eligibility before any approved PHI use.
- Plan for outages, budget holds, key rotation, and model behavior changes.
Accountable’s launch requirements
- Approved BAA, service terms, privacy notice and provider disclosure, with a verified self-service acceptance flow. Changes to any required document invalidate the previous activation record without overwriting the historical signed copy.
- Provider commercial permission, BAA scope, retention, regional controls, and exact model eligibility.
- Production identity, deployment, secrets, monitoring, and independent audit evidence.
- Verified email, payment processing, reconciliation, refunds/disputes, and incident processes.
- End-to-end synthetic testing through the deployed path.
These are Accountable’s operating requirements. Customers should not be asked to negotiate our provider agreements or repeat our infrastructure review during routine onboarding.
Availability and support
No production uptime SLA, response-time guarantee, public rate-limit upgrade process, or public support response commitment is established by the preview. Documentation and a successful local test do not substitute for production approval.