generated: '2026-08-09' method: searched docs: https://api.wegtultrarich.org/README.md#access-and-rate-limits source: openapi/wegtultrarich-openapi-original.yml summary: types: [none] api_key_in: [] oauth2_flows: [] public: true schemes: [] model: authentication: none authorization: none account_required: false api_key_required: false detail: >- "No authentication. No account. No personal information requested." The OpenAPI 3.0.4 document declares an empty top-level `security: []` and no `components.securitySchemes`, which matches the documented posture exactly — this is a deliberate open, read-only, computation-only API rather than a thin spec that omits its auth. mcp: url: https://api.wegtultrarich.org/mcp authentication: none session_state: none detail: 'No Mcp-Session-Id and no initialize handshake required; tools/list answers anonymously.' oauth_discovery_probed: - {url: 'https://api.wegtultrarich.org/.well-known/oauth-authorization-server', status: 404} - {url: 'https://api.wegtultrarich.org/.well-known/oauth-protected-resource', status: 404} - {url: 'https://api.wegtultrarich.org/.well-known/openid-configuration', status: 404} note_no_scopes: >- There is no OAuth surface, so no scopes/ artifact is emitted — an empty scopes file would misrepresent the model. access_controls_in_place_of_auth: - control: per-IP rate limiting detail: '100 req/min across /v1, 300 req/min for MCP, 500 req/min for docs' see_also: rate-limits/wegtultrarich-rate-limits.yml - control: CORS open by design detail: 'Access-Control-Allow-Origin: * so browser-side and agent-generated code can call directly' - control: read-only surface detail: 'GET-only; no state is created, so there is nothing to authorize' privacy: personal_data_collected: false detail: >- Technical request data is processed transiently for rate limiting, security and operations; the site uses privacy-first analytics only. policy: https://wegtultrarich.org/privacy-policy.html