Verify credentials

curl --request GET \
  --url https://api.reasonmachines.com/v3/self \
  --header 'Authorization: Bearer <token>'

const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.reasonmachines.com/v3/self', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.reasonmachines.com/v3/self",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.reasonmachines.com/v3/self"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api.reasonmachines.com/v3/self")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "principal_type": "service_user",
  "service_user_id": "key_3f9a",
  "service_user_name": "ci-bot",
  "org_id": "org_8c2d1e",
  "scopes": [
    "run",
    "sessions:read",
    "repos:read"
  ]
}

{
  "error": "missing_bearer",
  "message": "Authorization required"
}

{
  "error": "missing_scope",
  "required_scope": "sessions:read"
}

{
  "error": {
    "type": "rate_limited",
    "message": "This API key exceeded its request-rate limit"
  }
}

Account

Verify credentials

Returns the principal behind the current credential, its granted scopes, and the organization it can act on. Call this first to discover your org_id and available capabilities.

REST quickstart

A Reason is the long-running agent a person keeps: its own conversation, instructions, Loops (standing work woken by a schedule or an event) and the Sessions it runs. Give it work by messaging it.

Create a key at reasonmachines.com/customize?tab=api (Settings > API). Send it only in Authorization: Bearer <key>, never in a URL.
Call this endpoint and keep the returned org_id.
List your Reasons with GET /v3/organizations/{orgId}/reasons (sessions:read). Your main Reason comes first; create a named one with POST /reasons (run).
Message it with POST /v3/organizations/{orgId}/reasons/{reasonId}/messages (run) and read its replies with GET on the same path. Configure it with PATCH /reasons/{reasonId} (instructions, default model, default repositories), give it standing work with POST /reasons/{reasonId}/loops (automations:write), and read or edit memory with /memory/files, /memory/file and /memory/search (scope=personal for the key owner’s own, team for the workspace’s; memory:read, memory:write).
For one unattended task, start a Session instead: POST a prompt to /v3/organizations/{orgId}/sessions with reason_id, completion_mode: run_outcome and an idempotency_key in the JSON body (HTTP 201 creates; 200 replays). Poll it with GET until status leaves running. Lifecycle exit does not prove success: only outcome success is a successful task; failure, action_required and null need handling. Follow Retry-After on HTTP 429.

Runnable Node.js example

Download api-session.mjs, review it, and run it with Node.js 20 or newer. It creates real work that may incur usage. Set REASON_API_KEY, REASON_PROMPT, and a stable REASON_IDEMPOTENCY_KEY in your environment, then run node api-session.mjs. Optional REASON_REPO and REASON_PROJECT_ID (a Reason id) select resources explicitly. The example exits nonzero for failed, suspended, unresolved, or action-required tasks and times out after ten minutes without cancelling the remote session.

MCP is a separate client connection

For an MCP client, connect to https://mcp.reasonmachines.com/mcp using that client’s supported OAuth setup. See Connect over MCP for the commands. The REST workflow above uses the HTTP API and does not require installing an MCP client.

_{Auth: any valid API key (no scope)}

GET

self

Verify credentials

curl --request GET \
  --url https://api.reasonmachines.com/v3/self \
  --header 'Authorization: Bearer <token>'

const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.reasonmachines.com/v3/self', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.reasonmachines.com/v3/self",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.reasonmachines.com/v3/self"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api.reasonmachines.com/v3/self")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "principal_type": "service_user",
  "service_user_id": "key_3f9a",
  "service_user_name": "ci-bot",
  "org_id": "org_8c2d1e",
  "scopes": [
    "run",
    "sessions:read",
    "repos:read"
  ]
}

{
  "error": "missing_bearer",
  "message": "Authorization required"
}

{
  "error": "missing_scope",
  "required_scope": "sessions:read"
}

{
  "error": {
    "type": "rate_limited",
    "message": "This API key exceeded its request-rate limit"
  }
}

Authorizations

Authorization

string

header

required

Your Reason API key from Settings › API keys. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, devices:read, devices:write, devices:use, computers:read, computers:write, ssh:write, knowledge:read, memory:read, memory:write, skills:read, skills:write, pages:read, pages:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, network:read, network:write, automations:read, automations:write, agent_auth:read. devices:write, devices:use, computers:read, computers:write, ssh:write, network:read and network:write are opt-in, excluded from default keys. computers:read lists visible cloud and connected computers without waking them or granting execution access. devices:read discovers local Device targets; devices:use separately consents to local execution, so a discover-and-run local workflow needs both. devices:write manages enrollment and device grants; computers:write creates or deletes cloud computers; ssh:write manages retained SSH access. network:read reads the saved workspace network policy; network:write replaces custom allowed hosts and requires a current organization owner/admin. Legacy project PATCH requests containing network_allowed_hosts also require network:write plus their existing run scope and project management permission; saved project hosts do not affect current session egress. Only owners/admins can mint or manage keys with network:write; keys cannot grant themselves more authority. See /docs/network-policies for replacement semantics and runtime applicability. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:read reads sessions, including the assistant, reasoning and tool activity in their events. sessions:debug is privileged: only for organization owners/admins, it expands session events to the full diagnostic projection (diagnostic event kinds, status text and raw event metadata).

Query Parameters

cloud_activation

enum<string>

Include the current cloud activation state for this credential's workspace. Does not start work or reserve credit.

Available options:

1

Response

The authenticated principal.

principal_type

enum<string>

required

API keys resolve to service_user; MCP OAuth grants resolve to user.

Available options:

service_user,

user

org_id

string

required

Organization pinned to the current credential.

scopes

string[]

required

Capabilities granted to the current API key or OAuth token.

service_user_id

string

Present when principal_type is service_user.

service_user_name

string | null

Present when principal_type is service_user.

user_id

string

Present when principal_type is user.

user_name

string | null

Present when principal_type is user.

string | null

Present when principal_type is user.

organization_name

string | null

Display name of the organization pinned to this credential.

organization_slug

string | null

URL slug of the organization pinned to this credential.

cloud_activation

object | null

Optional cloud entitlement read requested with cloud_activation=1. Null when this flow is unavailable; readiness does not reserve credit or compute.

Show child attributes

capabilities_url

string

Present only for an admin API key (its single scope is the admin scope): where that key's admin capabilities are documented.

mcp_connections

object[]

Present when principal_type is user: active MCP OAuth client grants for the signed-in user and organization.

Show child attributes

Overview

Endpoints

Verify credentials

REST quickstart

Runnable Node.js example

MCP is a separate client connection

Authorizations

Query Parameters

Response