Get Me
const url = 'https://api.nuntius.chat/public/v1/me';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.nuntius.chat/public/v1/me \ --header 'X-API-Key: <X-API-Key>'Return the caller’s tenant id, key prefix, EFFECTIVE scopes, plan and rate-limit ceiling.
rateLimit (API-3 verification, D-API-2) is the REAL per-plan ceiling this SAME request
was just checked against inside require_public_api_caller (public_api_plan_limits,
pro/enterprise/uso_libre – never a placeholder or a hardcoded constant): it is
exactly what X-RateLimit-Limit on THIS response already carries, restated in the body for
a caller that only reads JSON. A plan downgrade between two calls changes it on the very next
request, same as every other gate in require_public_api_caller.
Permiso necesario: ninguno (además de una clave válida y con plan Pro o Enterprise)
Authorizations
Sección titulada «Authorizations»Responses
Sección titulada «Responses»Successful Response
GET /public/v1/me – caller introspection.
Feeds the future MCP-propio (D-API-10, MCP-SERVER-1): it filters which tools it exposes by
this SAME scopes/plan pair, never a separate resolution mechanism. scopes is the
caller’s EFFECTIVE, already-narrowed set (key scopes intersected with the owner’s
api_key-medium grant, PA-5) – never the key’s raw sealed scopes alone.
object
The caller’s own plan-tiered /public/v1 rate-limit ceiling (D-API-2).
object
Examplegenerated
{ "tenantId": "example", "keyPrefix": "example", "scopes": [ "example" ], "plan": "example", "rateLimit": { "perMinute": 1, "perDay": 1 }}