xrpl.well_known_agents_json.agents_json_rate_limits_match_enforcement

Declared rate limits (60/300) match what flask-limiter actually enforces on agent-tier routes.

yellow Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.

Machine-readable status: /claims/xrpl.well_known_agents_json.agents_json_rate_limits_match_enforcement.json or send Accept: application/json on this URL. URI is permanent — safe to cite.

What this claim says

label: Declared rate limits (60/300) match what flask-limiter actually enforces on agent-tier routes.
page: /.well-known/agents.json
claim id (yaml): agents_json_rate_limits_match_enforcement
behavior: MANUAL_CURATION
Layer 3 source: self-attested-only

Risk note

Enforcement shipped Day 6 (2026-08-02). Anonymous = 60/min, identified AI-crawler UA = 300/min, both per-IP via CF- Connecting-IP. Contract stays live via the paired regression test that reads the module's default-rate strings and asserts the two "60"/"300" substrings appear in agents.json rate_limits copy. Any future change to agent_tier_limit_rate() defaults MUST update _AGENTS_JSON.rate_limits and methodology.html's "For AI agents" rate-limits block in the same commit — the test guards the numeric match but not the surrounding prose.

Evidence — code paths that back this claim

app.py:_AGENTS_JSON (rate_limits block)
agent_tier_rate_limit.py:agent_tier_limit_rate() (source of truth for enforced values)
app.py: @limiter.limit(agent_tier_limit_rate) decorators on 8 agent-tier routes
tests/test_agent_tier_rate_limit.py:test_agents_json_rate_limit_copy_matches_module (regression guard)

Verify

CLAIMS.yaml on GitHub walker_health signed snapshot chain methodology · for AI agents

Sovereignty classification derives from the claim's Layer 3 source per /methodology. Last verified 2026-08-05. This surface is documented in docs/PAID_MACHINE_TIER_DESIGN.md § 3.1.