Codat
Based on public pricing signals, xpay observed that codat.io/pricing returns a 404. Documentation at docs.codat.io is open and a free developer sandbox is available, but production rates for accounting/commerce/banking integrations are reserved for a sales conversation. The shape is consistent with a unified-API SMB-data vendor that monetises through annual contracts.
Whoops, that page is gone
No tier numbers were visible on the public pricing page. An agent has no machine-readable path to evaluate or transact.
Snapshot rendered from xpay's extracted pricing signals. Tier count capped at 5 (anti-slider). For the live page, see source link above.How Codat scores on the 7 agent-ready dimensions
Public pricing
0 / 15
Usage-based / metered
0 / 25
Self-serve checkout
0 / 15
Public API
8 / 15
Low / no minimum
0 / 10
Unauth automated payment
0 / 10
Bonus (machine-readable pricing)On top of /100 base
0 / 5
Total
8 / 100
Six-step check: can an agent actually buy from Codat?
Discover price
https://www.codat.io/pricing/ — 404Select a plan
No tiers visible on codat.ioPay per task
No per-unit price publishedAvoid a sales call
Sandbox is self-serve at https://app.codat.io; production via salesAPI docs without auth
https://docs.codat.io accessibleEstimate cost upfront
No per-unit price exposedPros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-03. Not a review of the product — only of its current pricing posture for agent buyers.- API documentation is reachable without a login — discovery and integration can happen in one session.
- No tier numbers were visible on the public pricing page during the scoring fetch — agents cannot evaluate cost without a sales conversation.
- No per-unit price was advertised, so an agent has no way to estimate the cost of a single task.
- All advertised tiers route to a sales contact form; an agent cannot complete a purchase autonomously.
- No /.well-known/ai-pricing.json or equivalent machine-readable pricing manifest is published — agents must rely on HTML scraping.
- The pricing URL did not render numeric tier data on the scoring date — possibly a router or sales-led landing page.
How Codat could lift its score
- Publish a /pricing page with at least per-active-connection or per-pull rates for the accounting, commerce, and banking product families.
- Allow card-based production billing for sub-$1k/mo traffic from the existing dashboard.
- Expose /.well-known/ai-pricing.json so agents can compare Codat with Rutter and Apideck programmatically.
| pricing_visible | false |
| headline_phrasing | Whoops, that page is gone |
| tier_count | 0 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | null |
| per_unit_price | null |
| annual_required | null |
| self_serve_paid_tiers | 0 |
| sales_only_tiers | 0 |
| public_api_docs_url | https://docs.codat.io |
| api_docs_auth_walled | false |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
Codat
8
/ 100 (rubric v1.1)Financial Data APIs
Whoops, that page is gone
0
No
Sales-led
0 / 0
Public
No
Not published
2026-05-03