Skip to main content

Pay with Airi

Sign up for Airi and breeze through checkout. Save your payment details once, then check out in seconds anywhere Airi is accepted.

Agent score▲ 6.5
67.4/100OK
Embed
Claim this domain
Rank
Top 70%
#364
Finance rank
Sector average 73.1
#39 of 53
Benchmark runs
3 providers
1
Where this site sits
Finance average 73.1
−5.7
Market average 72.5
−5.1
Trend67.4One run so far. The trend fills in as the Index re-runs it each month. It sits 5.7 below the Finance average.Weakest area33.8Market ranking: Where do you sit in the lineup? Strongest is Brand awareness, at 92.5.Best agent73.5Gemini. ChatGPT Agent trails at 67.8.Where agents get stuck20 issues4 high severity. Worst: Homepage ships little text to server-rendered HTML. Agents without a browser see an empty shell.Technical readiness26/1006 essential checks failing, of 8. Protocol baseline by Is Agentic.
Opportunity cost · finance

Pay with Airi could see ~$55,420,000 of processed value exposed to agent-led journeys each year

Public agent-traffic forecasts suggest a growing share, modeled here at roughly 34%, of account opening and transaction initiation sessions in the finance sector could be initiated or completed by AI agents[1][2]. Pay with Airi currently scores 67.4 on the Index[3], roughly 5.1 points below the finance peer average, leaving a 33-point gap to the ideal agent experience (100). The illustrative figure below applies that gap to the agent-driven slice of a typical annual processed transaction value baseline for this sector. It is a directional estimate, not a measured conversion rate.

Gap to leader
32.6 pts
Below finance avg
5.1 pts
Modeled flows at risk
$55,420,000

Estimate assumes a $500M annual processed-value baseline. Claim your domain to replace this placeholder with your reported processed value.

Sources
  1. [1]Gartner (2025): Intelligent Agents in AI Really Can Work Alone. Here’s How.
  2. [2]Adobe Analytics (2025): Generative AI traffic to U.S. retail sites (weekly trend)
  3. [3]Stunt Double (2026): Stunt Double Index methodology & scoring rubric

Category breakdown

Strongest is Brand awareness; weakest is Market ranking.

Brand awarenessCan agents recognize you exist?
93
▲ 10.1
DiscoveryWill they pick you?
47
▼ 10.8
Information retrievalCan they read your site?
69
▲ 6.5
Market rankingWhere do you sit in the lineup?
34
▲ 33.8
AccuracyDo they tell the truth about you?
91
▲ 14.8
Task completionCan an agent complete a task on behalf of a user?
58
▼ 8.4
Delegated accessDo you let agents in, safely?
67
▲ 66.7
Contact & communicationCan an agent reach a human?
43

Score over time

Every run against the Finance and market medians.

One run so far, on 29 Sept 2026. The line fills in as the Index re-runs it each month.

  • This site
  • Finance median
  • Market median
60708090MayJunJulAugSept
Each category over time
  • Brand awareness93
  • Discovery47
  • Information retrieval69
  • Market ranking34
  • Accuracy91
  • Task completion58
  • Delegated access67
  • Contact & communication43
Every run, as a table
RunThis siteFinance medianMarket median
29 Sept 202667.479.876.3

Medians are by month: each domain counts once, at its newest run that month. Dates are UTC. Latest run 29 Sept 2026.

Agents

Gemini does best. Each provider's model and every session behind its score.

73.5
How these are scored

The score beside each provider is its session quality over a rolling 30 days, from at least 10 sessions per provider.

Scores run 0 to 100. Each is one agent on one task, graded against that task’s fixed rubric, so no agent marks its own work. The median under a score is the sector median: the middle score for the same category, or the same provider, across the other Finance sites the Index has sent agents to.

  • Excellent85+
  • Good72-84
  • OK58-71
  • Poor40-57
  • Critical<40

Latest run 29 Sept 2026 (UTC). Anyone signed in can re-run it from 30 Sept 2026, 17:17 UTC.

ClaudeAnthropic
08 tasks72.9
Latest run average72.9median 100.0
  • Market ranking
    market-ranking-ecom-v2 · 9s
    43median 60 Done
  • Contact & communication
    support-ecom-v1 · 48s
    43median 66 Done
  • Delegated access
    delegated-access-ecom-v1 · 2m 10s
    89median 64 Done
  • Discovery
    journey-ecom-v1 · 2m 47s
    49median 51 Done
  • Task completion
    journey-ecom-v1 · 2m 49s
    49median 88 Done
  • Brand awareness
    research-ecom-v1 · 3m 13s
    98median 91 Done
  • Information retrieval
    research-ecom-v1 · 3m 15s
    76median 52 Done
  • Accuracy
    research-ecom-v1 · 3m 13s
    99median 84 Done
ChatGPT AgentOpenAI
06 tasks67.8
Latest run average67.8median 100.0
  • Market ranking
    market-ranking-ecom-v2 · 20s
    43median 60 Done
  • Delegated access
    delegated-access-ecom-v1 · 7m 42s
    85median 64 Done
  • Task completion
    journey-ecom-v1 · 8m 28s
    58median 88 Done
  • Discovery
    journey-ecom-v1 · 8m 26s
    0median 51 Done
  • Brand awareness
    research-ecom-v1 · 9m 33s
    100median 91 Done
  • Information retrieval
    research-ecom-v1 · 9m 34s
    65median 52 Done
GeminiGoogle
07 tasks73.5
Latest run average73.5median 100.0
  • Market ranking
    market-ranking-ecom-v2 · 10s
    43median 60 Done
  • Delegated access
    delegated-access-ecom-v1 · 4m 50s
    76median 64 Done
  • Discovery
    journey-ecom-v1 · 6m 15s
    43median 51 Done
  • Task completion
    journey-ecom-v1 · 6m 17s
    46median 88 Done
  • Accuracy
    research-ecom-v1 · 7m 29s
    100median 84 Done
  • Brand awareness
    research-ecom-v1 · 7m 29s
    98median 91 Done
  • Information retrieval
    research-ecom-v1 · 7m 30s
    76median 52 Done

Where agents get stuck

20 issues, worst first.

The public summary. Verified owners can replay every session in full.

HighInformation retrieval
Homepage ships little text to server-rendered HTML. Agents without a browser see an empty shell.
HighDelegated access
No discoverable MCP server. ChatGPT apps and Claude connectors have no scoped way to call your product; agents must drive a browser instead.
HighDelegated access
No public API docs detected. Agents have no scoped way in; they must drive a browser.
HighContact & communication
No contact page linked or reachable. Agents acting on a user’s behalf have nowhere to send a message.
Show 16 more issues
MediumBrand awareness
No Organization JSON-LD. Agents can’t tell who owns the site at a glance.
MediumDiscovery
No robots.txt. Agents fall back to defaults and may miss crawl hints.
MediumDiscovery
No sitemap.xml. Agents can’t enumerate indexable pages.
MediumInformation retrieval
No JSON-LD structured data. Agents must infer entities from markup.
MediumMarket ranking
No Product/Service schema on the homepage. Agents can’t easily compare offerings.
MediumMarket ranking
No price visible to non-JS clients. Agents may report "pricing not disclosed".
MediumAccuracy
No JSON-LD at all. Every factual claim must be inferred from prose.
MediumTask completion
No mention of delegated auth primitives (passkey, OAuth, MCP). Agents must drive a full browser session.
MediumDelegated access
No OAuth/OIDC discovery metadata. Agents cannot bootstrap a scoped, revocable session; any delegation falls back to password sharing.
MediumContact & communication
No contact email visible in server-rendered HTML. Agents can’t fall back to email.
LowBrand awareness
Fewer than two social profiles linked. Agents struggle to triangulate the brand.
LowDiscovery
No canonical URL. Agents may conflate duplicate pages as separate entities.
LowMarket ranking
No review or aggregateRating schema. Agents have no signal for ranking vs peers.
LowAccuracy
No canonical URL. Agents may cite ephemeral query-string variants.
LowAccuracy
No privacy policy linked from the homepage. Agents can’t cite policy when asked.
LowTask completion
No detectable agentic-commerce rail (Stripe SPT, Shopify/UCP, PayPal ACP). Agent-initiated payment needs custom work.

Want to find these in your own flows before an agent does? Read how to test your product for AI agent users.

Technical readiness

The protocol baseline: robots, sitemaps, llms.txt, structured data and more.

26/100

Protocol baseline by Is Agentic

Score
26/ 100
Agents are likely to struggle
Essential
20/ 80
2 of 8 passing
Recommended
5/ 20
3 of 14 passing
Bonus
+0.8
4 positive signals
Fail
Content without JavaScriptessential
Very little text content (58 chars) - likely JS-rendered, invisible to AI crawlers
Fix: Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Fail
Agent-friendly 404sessential
Nonexistent paths return HTTP 200 with the app shell (soft-404). Agents probing for resources conclude every path exists. Return a real HTTP 404 status for unknown paths.
Fix: This check awards partial credit for a real HTTP 404/410 status and full credit when a Markdown error body is also available. If the status is already correct, keep it and add the Markdown body. Include at least 20 characters explaining the error and point agents to your docs, sitemap, or llms.txt. Verify with `curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist`. Check both the final 404/410 status and the Markdown body, served with Content-Type: text/markdown. A correct status with an HTML error page still earns only partial credit.
Fail
Redirect hygieneessential
Redirect hygiene issues: the homepage looks like a JavaScript-redirect stub. Replace client-side redirects with HTTP redirects so non-JS agents follow them.
Fix: Replace meta-refresh and JavaScript-only redirects with real HTTP 301/302 redirects. Non-JS agents never execute `location.href` or wait for a meta refresh - they see only the stub page. Verify with `curl -sI <url>` - you should see a Location header, not a 200 with a near-empty body.
Show 14 more issues
Fail
OpenAPI spec publishedessential
No OpenAPI/Swagger specification found
Fix: Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Fail
JSON error responsesessential
API does not return JSON error responses (or no API detected)
Fix: Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
Fail
Markdown content negotiation (acceptmarkdown.com)essential
Homepage https://airi.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none")
Fix: Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with `curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/` and `curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/`. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Fail
Developer resource discoverabilityrecommended
Agent searched for "airi" developer resources but found nothing relevant
Fix: Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
Fail
Public API with reachable endpointsrecommended
No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
Fix: Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
Fail
JSON-LD structured datarecommended
No JSON-LD structured data found on homepage
Fix: Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
Fail
Public API/docs linked from homepagerecommended
No public API or documentation page linked from homepage
Fix: Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
Fail
Agent instruction / when-to-userecommended
No agent instruction file with when-to-use guidance found
Fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.
Fail
API schema complexity analysisrecommended
No API schema detected
Fix: Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.
Fail
Function calling compatibilityrecommended
No API spec found - function calling requires discoverable endpoints
Fix: Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
Fail
Sitemap existsrecommended
No sitemap found
Fix: Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.
Fail
Organization schema completenessrecommended
No JSON-LD found - Organization schema missing
Fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Fail
Trust anchor pagesrecommended
No trust anchor pages found with sufficient content (About, Contact, Privacy)
Fix: Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
Partial
Metadata completenessrecommended
2/4 metadata signals present - missing: canonical URL, HTML lang attribute
Fix: Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
22 checks · scanned 29 Sept 2026

Embed

Put this score on your site

A live badge for your footer, docs or README. It updates after every run and links back to this report.

airi.com Stunt Double Index agent score badge