# Ibotta — API Agent Score

> Score: 52/100 (Grade: D) | Domain: ibotta.com | Rubric: 1.0.0 | Checked: August 7, 2026

Ibotta scored 52/100 (D), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/ibotta)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 52/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 50/100 (D)
- Developer Experience: 55/100 (D)
- Agent Discovery: 70/100 (B)
- Agent Understanding: 57/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [fail] Example coverage — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://ibotta.com/register; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 5 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 63%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://dashboard.ibotta.com/docs/llms.txt, https://dashboard.ibotta.com/llms.txt); candidates redirected cross-host to https://auth.dashboard.ibotta.com (agents can't follow cross-host redirects); 2 rate-limited (HTTP 429). Investigated: docs 33%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Ibotta's API program shows meaningful strength in agent discoverability, but two critical gaps are putting partner success at risk: partners and their AI agents lack the executable context and machine-readable instructions needed to integrate confidently, and the onboarding experience is missing the quickstarts and code samples that drive a fast first call. Closing the runnable-truth and agent-understanding gaps should be the top priority, followed immediately by shoring up API design completeness and onboarding quality — together these will materially compress partner time-to-integration and reduce support burden.