Meta
Meta API
The API's self-describing entry point: a health check confirms the service is up and the method catalog tells you which platform method to call; none of it needs authentication.
Base URL
Loading…
Get started
Loading…Endpoints
| Method | Path | Description | Support |
|---|---|---|---|
| GET | /v1/health | Health check | ● Supported |
| GET | /v1/methods | Search platform methods | ● Supported |
| GET | /v1/methods/{name} | Retrieve a platform method | ● Supported |
Differences from Praxis
- Meta is the platform's self-describing face and mirrors no third-party API; healthCheck and the method catalog need no authentication; healthCheck returns the plain text
ok. - Search platform methods：A nonempty q searches by relevance over method name, summary and description, ignoring word order and case; limit is an integer from 1 to 50 (default 20). Without q, or with whitespace only, methods are listed by name; limit is 1 to 200 (default 50). When has_more is true, pass last_id unchanged as after_id for the next page. Search ignores after_id. An out-of-range limit returns 400 INVALID_PARAMS. The catalog covers platform methods (praxis.*) only, not the MCP tools of a session.
- Retrieve a platform method：name comes from the search results and must match the method name exactly. The declaration is never truncated; copy field names and enum values from it. An unknown name returns 404 METHOD_NOT_FOUND whose hint lists up to three similar names.
Meta is self-describing: /meta/v1/openapi.yaml returns the full OpenAPI spec for the current environment, which is authoritative for parameters and fields.
Errors follow the problem+json format, see errors; quotas and response headers are covered in rate limits.