---
title: "getactuators auth.md"
description: "No credentials needed: anonymous, read-only access to the REST API and MCP server."
canonical: https://getactuators.com/auth.md
last-updated: 2026-09-26T20:29:50.000Z
---
# getactuators auth.md

> How an agent authenticates to getactuators: it does not need to. The REST API (https://getactuators.com/api) and the MCP server (https://getactuators.com/mcp) are public, anonymous and read-only.

## Discover

There is no authorization server, so there is no OAuth protected-resource metadata and no agent_auth block to fetch. The machine-readable descriptions of what you can call are https://getactuators.com/openapi.json (REST) and https://getactuators.com/.well-known/mcp/server-card.json (MCP). No endpoint answers 401 or sends a WWW-Authenticate challenge.

## Pick a method

One method is supported: anonymous access. In auth.md terms the only identity type is anonymous; identity_assertion, service_auth and ID-JAG exchanges are not used because nothing is gated.

## Register

No registration. There is no client registration endpoint, no API key to request and no account to create.

## Claim

Nothing to claim. No user account exists that an agent could be linked to.

## Exchange

No token exchange. There is no token endpoint.

## Use the access_token

Send requests without an Authorization header. Examples:

```bash
curl https://getactuators.com/api/v1/actuators?use_case=quadruped_leg&sort=torque_density_nm_per_kg
```

For MCP, point any Streamable HTTP client at https://getactuators.com/mcp with no credentials.

## Errors

- 404: the id or path does not exist. Under /api the body is JSON (application/problem+json).
- 400: a query parameter or request body is invalid.
- 429: more than 120 requests per minute from one IP. Wait for Retry-After, then retry.
- No 401 or 403 is ever returned for missing credentials.

## Revocation

Nothing to revoke: no tokens or keys are issued. If access ever becomes gated, this document will describe the flow first.