agent · voice ai agents

Hamming AI

hamming.aievidence retrieved Aug 2, 2026 – Aug 15, 2026view as JSON all voice ai agents entries 48 alternatives

Indexed12 or more fields evidenced; not yet scored by a human against the rubric

23 fields evidenced · 36 with no public information. Every value below links to the document it came from and the date we checked it.

19 of those are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist

1 of those is flagged for review: our own check found language in the cited source that may address the field. An editor has not adjudicated it yet.

Also appears in

AI agents and vendors that state SOC 2 AI agents and vendors that state HIPAA compliance AI agents and vendors that state SOC 2 Type II AI agents that state scoped or role-based permissions

Trust gap

How this is scored

These scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.

Runtime governance

2/3 auto

Are scope, spend, and authority enforced while the agent runs?

Scored from 2 evidenced field(s): runtime_governance, permission_scopes. Automated score; capped at 2 pending review.

Counts Runtime governance and Permission scopes, each cited below.

Audit trail

1/3 auto

Is there a tamper-evident record of what it actually did?

Scored from 1 evidenced field(s): audit_trail. Automated score; capped at 2 pending review.

Counts Audit trail, each cited below.

Compliance

2/3 auto

Are compliance obligations attached per engagement?

Scored from 2 evidenced field(s): compliance_certs, regulatory_alignment. Automated score; capped at 2 pending review.

Counts Regulatory alignment and Compliance certifications, each cited below.

Outcome settlement

unscored

Does payment depend on a verified result?

Insurance & indemnity

unscored

Can the deployment be insured, and is the customer indemnified?

Assurance

Insurance available: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Own liability cover: no public information
hamming.ai · checked Aug 15, 2026 · source did not state this
Insurance carriers: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Coverage limits: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Indemnification: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Liability cap: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Audit trail: not yet interpreted
“Audit logs export to our SIEM via webhooks for complete visibility.”
hamming.ai · checked Aug 2, 2026
Tamper-evident log: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Explainability: not yet interpreted
“We evaluate holistically. Did the caller's goal get accomplished? That's what matters - not whether each turn matched a script exactly.”
hamming.ai · checked Aug 2, 2026
Runtime governance: not yet interpreted
“RBAC ensures contractors only access testing environments - not production PHI data.”
hamming.ai · checked Aug 2, 2026
Permission scopes: not yet interpreted
“RBAC ensures contractors only access testing environments - not production PHI data.”
hamming.ai · checked Aug 2, 2026
Compliance certifications: not yet interpreted
“SOC 2 Type II • HIPAA (BAA available)”
hamming.ai · checked Aug 2, 2026
Regulatory alignment: not yet interpreted
“SOC 2 Type II certified, HIPAA-ready with BAA support.”
hamming.ai · checked Aug 2, 2026
Outcome-based pricing: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Settlement mechanism: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Asset custody: Payment data custody held by Stripe, a named third-party payment processor.
“All payment data is stored by Stripe.”
hamming.ai · checked Aug 15, 2026
Dispute process: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
SLA terms: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Evaluation coverage: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Self-reported performance: no public information
hamming.ai · checked Aug 15, 2026 · source did not state this

Agency

Autonomy level: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Human oversight: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Goal complexity: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Action space: no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
hamming.ai · checked Aug 2, 2026
Operating environment: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Initiative: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this

Safety

Safety evaluations: not yet interpreted
“Pre-built security packs test for jailbreak attempts and PII disclosure before production.”
hamming.ai · checked Aug 2, 2026
Red teaming: not yet interpreted
“Red-team risky behavior before it reaches customers.”
hamming.ai · checked Aug 2, 2026
Safety policy: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Usage restrictions: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Model or system card: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Incident reporting: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Third-party evaluations: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Data handling: not yet interpreted
“US-only data residency, customer-managed encryption keys, and complete data isolation with single-tenant deployment gives us enterprise-grade security.”
hamming.ai · checked Aug 2, 2026

Practicality

Pricing model: not yet interpreted
“We offer startup and SMB-specific pricing designed to match your usage.”
hamming.ai · checked Aug 2, 2026
Price point: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Availability: not yet interpreted
“Sign up Request a Demo”
hamming.ai · checked Aug 2, 2026
Deployment options: not yet interpreted
“single-tenant deployment”
hamming.ai · checked Aug 2, 2026
Integrations: Vapi, Retell, 11Labs
“Import agents from Vapi, Retell, 11Labs, or any orchestration framework.”
hamming.ai · checked Aug 2, 2026
Supported regions: not yet interpreted
“US-only data residency”
hamming.ai · checked Aug 2, 2026
Support model: not yet interpreted
“enterprise customers get custom plans with dedicated support and compliance features”
hamming.ai · checked Aug 2, 2026

Foundation models

Base models: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Model provider: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Model swappable: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Open weights: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Fine-tuning: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Context window: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this

Ecosystem

Protocols supported: not yet interpreted
“REST APIs for everything. Webhooks that actually work.”
hamming.ai · checked Aug 2, 2026
Tool use: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Multi-agent: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
API access: not yet interpreted
“REST APIs for everything.”
hamming.ai · checked Aug 2, 2026
Open source: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this
Marketplace presence: no public information
hamming.ai · checked Aug 2, 2026 · source did not state this

Impact

User base: not yet interpreted
“10K+ agents monitored”
hamming.ai · checked Aug 2, 2026
Deployment scale: not yet interpreted
“Enterprise load tests across inbound, outbound, and WebRTC”
hamming.ai · checked Aug 2, 2026
Target sectors: high-growth startups, banks, and healthtech companies
“Trusted by high-growth startups, banks, and healthtech companies where reliability matters”
hamming.ai · checked Aug 2, 2026
High-risk domains: high-stakes domains where mistakes lead to churn, compliance issues, or lost revenue.
“We help teams in high-stakes domains where mistakes lead to churn, compliance issues, or lost revenue.”
hamming.ai · checked Aug 2, 2026
Documented incidents: not yet interpreted
“Hamming saved us a lot of headaches. We caught a critical bug. The agent was saying 'I booked your appointment' but didn't actually book it. We killed it before any customer saw it.”
hamming.ai · checked Aug 2, 2026
Market recognition: no public information
hamming.ai · checked Aug 15, 2026 · source did not state this