Layer
Layer's pricing page did not render numeric tier data on the scoring date. No per-unit price was found on the page; an agent has no direct way to estimate the cost of a single task. No public API documentation URL was discovered.
Layer pricing
We’re still verifying Layer’s pricing
Pricing page shows a free tier but no public paid pricing; therefore most pricing fields are null and model type is set to unverified.
Source of truth: layer.cafe/
How Layer scores on the agent-ready dimensions
Public pricing
0 / 15
Usage-based / metered
0 / 25
Self-serve checkout
0 / 15
Public API
0 / 15
Low / no minimum
0 / 10
Unauth automated payment
0 / 10
Bonus (machine-readable pricing)On top of /100 base
0 / 5
Total
0 / 100
Six-step check: can an agent actually buy from Layer?
Discover price
Select a plan
Pay per task
Avoid a sales call
API docs without auth
Estimate cost upfront
Pros and cons for AI agents
Observational summary written by xpay from the signals captured on 2026-05-06. Not a review of the product — only of its current pricing posture for agent buyers.- Pricing is publicly visible on an indexable page — agents can read tiers without scraping past auth.
- 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.
- API documentation is gated or absent; an agent cannot inspect the integration surface without authentication.
- 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 Layer could lift its score
Add a per-unit price (e.g. $X / 1K calls) to the pricing page so an agent can compute its own cost before committing.
| pricing_visible | false |
| headline_phrasing | Your goals, visualized and achieved effortlessly! — Started using layer to create some App and WebSite Sitemaps. Really liking it. Easy to use. Good to see that "User Flows" appear to be in the Product Roadmap as well. |
| tier_count | 0 |
| lowest_paid_entry_usd | null |
| free_tier | false |
| free_tier_terms | null |
| per_unit_price | null |
| annual_required | false |
| self_serve_paid_tiers | 0 |
| sales_only_tiers | 0 |
| public_api_docs_url | null |
| api_docs_auth_walled | null |
| ai_pricing_json_present | false |
| agents_txt_present | false |
| anonymous_purchase_path | false |
| per_unit_classification | null |
| usage_headline_present | false |
| custom_tier_present | false |
| agent_friendly | {"ai_pricing_json":false,"agents_txt":false,"llms_txt":false,"sitemap_xml":true,"mcp_server_card":false,"agent_skills_index":false,"x402_supported":false} |
View raw extracted page text →
Claim this scorecard & lift your score.
Get the breakdown of every signal we measured, the one-line fix, and how your peers in Mind Mapping stack up.
Compare the agent-ready picks in Mind Mapping.
If you're building or running an AI agent that needs to buy from this category, see who's scoring highest right now.
See agent-ready picksLayer
0
/ 100 (rubric v1.1)Mind Mapping
Not advertised
0
No
Sales-led
0 / 0
Auth-walled
No
Not published
2026-05-06
Discovery files and protocols
Side-channel signals — informational, not part of the score. Each protocol is independent; adoption signals the publisher is thinking about agent buyers.ai-pricing.json
agents.txt
llms.txt
sitemap.xml
MCP Server Card
Agent Skills
x402 / MPP
Compare Layer with peers
Highest-scoring companies in the same category that an AI agent might evaluate as an alternative.Mindomo
62
Thoughtflow
58
iMindQ
50
XMind
49
MindMeister
49
Bubbl.us
49
NovaMind
49
Ideamap
49
Explore the Agent-Ready SaaS Index
25,480+ SaaS scored on agent-buyability — browse by readiness band, category, or jump straight to a pay-per-run tool on xpay.tools.