# Prescient AI Agent Authentication

The Prescient AI public REST API and public MCP servers are anonymous, read-only discovery surfaces. They expose only information already published on prescientai.com. They cannot access or change customer accounts, datasets, models, forecasts, or recommendations.

## Discover

Start at [the developer portal](https://prescientai.com/developers), [OpenAPI specification](https://prescientai.com/openapi.json), or [MCP server card](https://prescientai.com/.well-known/mcp/server-card.json). The machine-readable auth policy is: no credential required.

## Pick a method

Use the anonymous method. Do not send cookies, bearer tokens, identity assertions, or API keys. The OpenAPI document intentionally declares no security scheme for public operations.

## Register

Registration is not needed. There is no register_uri because no credential is issued. Prescient does not currently advertise an agent_auth registration flow, identity_assertion, or id-jag claim for this public surface.

## Claim

There is no claim step and no claim_uri. Successful requests return public data directly.

## Use the credential

No credential exists. Call HTTPS endpoints normally with an Accept header for JSON, markdown, or the MCP transport response. A WWW-Authenticate challenge is not returned because anonymous calls are permitted.

## Errors

REST failures return JSON containing error.code, error.message, error.hint, and error.documentation_url. MCP protocol failures use JSON-RPC 2.0 errors; tool failures return isError: true. A 401 indicates a configuration defect on these public routes, not a request for authentication.

## Revocation

There is nothing to revoke and no revocation_uri because the public API issues no credentials. Customer product access remains separate and is not exposed through this developer surface.