Requesty Human-Dependent

Pillar Scores

Executive Summary

Requesty scores 55/100 in the Human-Dependent tier — the highest-scoring company in recent audit cycles when it comes to Velocity Triggers (9/10), where its instant-activation model is genuinely best-in-class. The platform's LLM gateway infrastructure is fundamentally aligned with agent-native demand: the thing agents need most (LLM API access with intelligent routing) is exactly what Requesty sells, and they sell it with near-zero activation friction. The critical gaps are all in the signal layer: no schema.org markup, no published rate limits, and a status page that doesn't exist publicly mean that agents evaluating Requesty as a production dependency cannot verify its claims without human research. The highest-ROI fix is adding schema.org/Offer markup to the pricing page — a 2-hour task that would move Requesty meaningfully toward the 65+ Emerging tier and signal to the agent-native buyer community that the infrastructure they run on is infrastructure that speaks their language.

Strongest Signals

• Near-perfect Velocity Triggers (9/10) : Requesty's free tier with instant API key issuance, no credit card required, and single-line integration is the clearest example of agent-native activation in this audit series. An autonomous agent system can begin using Requesty with zero human involvement.
• llms.txt exists : Confirmed at docs.requesty.ai/llms.txt with a full version at docs.requesty.ai/llms-full.txt. This is a meaningful signal that the company understands LLM-native documentation, even if placement on a subdomain reduces discoverability.
• Semantically precise metrics : Claims are stated in specific, verifiable terms (8ms P50 latency, 99.99% uptime, 80% cache savings, 90B daily tokens) — rare in the LLM tooling category and directly usable by agents as evaluation criteria.
• RBAC + scoped access controls : Per-user budget limits, model whitelisting, and role-based access are better-than-average foundations for agent-scoped permissions, even without explicit agent scope tokens.

Critical Gaps

• No schema.org structured data : Homepage and pricing pages have no machine-readable Offer, Product, or AggregateRating markup. Agents that rely on structured signals for offer evaluation must fall back to HTML parsing — lossy and unreliable.
• No published rate limits or caps : Without documented throughput limits, an autonomous agent system routing production traffic through Requesty cannot perform capacity planning or set safe rate controls. This is a significant gap for enterprise agent deployments.
• No public status page : 99.99% uptime is claimed but unverifiable without a public status history. Agents operating in production need runtime-accessible uptime verification, not just marketing claims.
• Low switching costs by design : The platform's biggest adoption advantage (drop-in replacement) is its biggest retention vulnerability. Any competitor offering a marginally better deal faces near-zero migration friction. For agents optimizing cost over time, this makes Requesty a permanently contested position.

Priority Actions

1. Move llms.txt to root domain + expand it — +1 pts · P1 · Effort: Low
2. Add schema.org/Offer markup to pricing page — +3 pts · P1 · Effort: Low
3. Publish public status page + real-time uptime history — +2 pts · P3 · Effort: Low
4. Publish rate limits and throughput caps — +3 pts · P2 · Effort: Low

All 20 Criteria