Your first audit stays private until you publish it. Free for every vendor today.
Synthetic vendor, support agent
Synthetic demo data
Standard #1 · v0.11
Pooled across 3 customers
On synthetic data, audited resolution was 56.9% against 58.7% claimed, a 1.8-point gap; 1.8 of those points are conversations counted as resolved where the customer came back within 7 days.
Claimed
58.7%
50.6–66.3
Audited, judge-confirmed
56.9%
48.2–65.1
Gap, points
1.8
0.9–3.6
Claimed, by outcome, % of eligible
Audited
Repeat contact
95% interval
What you get. A score from your customers’ own data, a live badge, a signed attestation and a traction report.
An audited score from your customers’ own data
Every record of a rolling 30-day period, read from each customer’s own help desk, CRM or calendar with its consent, or streamed by your agent and reconciled by the customer. The claimed rate beside the audited rate, each with its 95% interval.
The badge is drawn from your current status each time it loads and links to your profile and its public changelog. A copy hosted anywhere else is not a badge.
A statement of your score and status, signed with Ed25519, that anyone can check. It expires 44 days after it is issued, and /verify says when a newer one replaces it.
{
"schema": "proven.attestation/1",
"issuer": "Attify",
"vendor": {
"name": "Synthetic vendor"
},
"product": "support agent",
"job_type": "support-resolution",
"standard": {
"id": "support-resolution",
"number": 1,
"title": "Attify Audited Resolution Standard",
"version": "0.11"
},
"rules_version": "5",
"status": "claim_confirmed",
"status_reason": "Audited resolution is 56.9% (95% interval 48.2% to 65.1%), 1.8 points below the claimed 58.7%: claim confirmed within 5.0 points, the gap's 95% interval (0.9 to 3.6 points) staying within the 5.0-point tolerance.",
"evidence_tier": "judge",
Attestation
Synthetic, unsigned
Vendor
Synthetic vendor, support agent
Standard
#1 · v0.11
Period
2 Aug – 23 Sept 2026
Audited
56.9% 48.2–65.1
Claimed
58.7%
Status
Claim confirmed · within 5.0 points
SignatureEd25519, added when issued
A traction report for fundraising
Usage, retention and audited outcomes over the months your customers’ data covers, signed, with share links that expire and a log of who viewed them. Free when an investor requests it.
Traction report
Usageper customer, per month
Retentionactive, new, retained, churned
Pilot to productionthe first week at the threshold
Concentrationthe largest customer, the largest three
Outcomesaudited, with 95% intervals
Claims testedup to five, each with its result
The sample attestation in full, as JSON
The score, its period, the standard and its version, the evidence tier, the status and why. This one is built from synthetic data and is not signed.
A real attestation adds its id, when it was issued and when it expires, the profile and badge addresses, and an Ed25519 signature that /verify checks against Attify’s published keys.
Sample attestation, synthetic and unsigned
{
"schema": "proven.attestation/1",
"issuer": "Attify",
"vendor": {
"name": "Synthetic vendor"
},
"product": "support agent",
"job_type": "support-resolution",
"standard": {
"id": "support-resolution",
"number": 1,
"title": "Attify Audited Resolution Standard",
"version": "0.11"
},
"rules_version": "5",
"status": "claim_confirmed",
"status_reason": "Audited resolution is 56.9% (95% interval 48.2% to 65.1%), 1.8 points below the claimed 58.7%: claim confirmed within 5.0 points, the gap's 95% interval (0.9 to 3.6 points) staying within the 5.0-point tolerance.",
"evidence_tier": "judge",
"period": {
"start": "2026-08-02",
"end": "2026-09-23"
},
"claimed_rate": {
"value": 0.5867,
"lo": 0.5065,
"hi": 0.6626
},
"audited_rate": {
"value": 0.5688,
"lo": 0.482,
"hi": 0.6515
},
"verified_rate": {
"value": 0.5688,
"lo": 0.482,
"hi": 0.6515
},
"gap": {
"value": 0.018,
"lo": 0.0088,
"hi": 0.0363
},
"claim_confirmed": true,
"claim_tolerance_points": 5,
"sample": {
"customers": 3,
"conversations": 1092
},
"summary": "On synthetic data, audited resolution was 56.9% against 58.7% claimed, a 1.8-point gap; 1.8 of those points are conversations counted as resolved where the customer came back within 7 days."
}
Why buyers ask for third-party data.
86% of B2B technology buyers agree or strongly agree that objective, third-party-authored content or data is critical for trusting thought leadership positions or claims.
How it works. Connect the data, audit with your customers, publish when you choose.
1
Connect the data
Your customers connect the system your agent works in (Intercom, Zendesk, HubSpot, Google Calendar, Microsoft 365 and more), read-only. Or connect your own agent platform or observability account, or stream each interaction through the Ingest API, an SDK or OpenTelemetry.
A score needs at least 3 independent customers. Each agrees to exactly what Attify reads and passes four independence checks; witnessed data also needs its consent and a monthly reconciliation. You see a private daily score from the first connection. Your first judged audit is private too: you see every number and choose whether to publish it.
3
Publish your badge
Once you publish, the score goes on your profile, the registry, the badge and a signed attestation. A new score is made every 30 days and publishes after a 7-day review. Without fresh data for 14 days, the status reads Lapsed.
Every vendor is free today. The first 10 vendors to open a program also keep it free for 12 months from their first published score once pricing starts, then 50% off, recorded on their account.
You see where you stand before anything is public: a private daily score from your first connected customer, a private report while you are below the publishing minimums, and a private first audit. Nothing publishes until you choose to. Once it does, the status reads Claim confirmed · within 5.0 points when the audit shows, with 95% confidence, that your count overstates audited outcomes by at most 5.0 points, and Claim not confirmed otherwise.
Until you publish, only you and Attify’s reviewers. Each customer sees its own results. You see each customer’s results and consent, never their conversations. Once published, the score, its status and the changelog are on your profile, behind your badge and in the attestation.
What happens if our score drops later?
Once you publish, every later score publishes too, whatever it shows. Each stays private for 7 days, where you can add one public comment, then replaces the last one; a published score cannot be hidden or edited. With no fresh data for 14 days the status reads Lapsed. If you stop verification, your profile reads Lapsed and keeps its full history. Each change is dated in the public changelog, and the badge always shows the current status.
Do our customers have to do anything?
Each one accepts your invitation, reads exactly what Attify will read, and connects its system read-only, which some companies put through a security review first. For an agent on your own platform, they consent and reconcile each month: their own total, then a spot check of 10 interactions. Attify also asks some of them directly whether they use your product.
How long does it take?
Counted from your third independent customer connecting: its first sync reads 90 days back at once, the independence checks run (a customer Attify asks directly has 14 days to answer), then your first judged audit, private until you publish it. About one to two weeks, given at least 3 customers and 500 AI-handled conversations in the 30-day period (sales meetings: 150 meetings over 90 days).
Is it independent if we pay?
The price never depends on a result: buyers pay by audited AI interactions and vendors by customers covered, never by a score. The standards and the judge’s instructions are published. Attify never advises a vendor on how to raise its score. Customers you invite must pass four independence checks, and a customer proven fake revokes the program in public.