For the complete documentation index, see llms.txt. This page is also available as Markdown.

API

Wayfound offers APIs to connect your agents to the platform. You can generate an API key on the Connections tab in the Settings page. Access to this page requires admin permissions on the Wayfound platform.

Learn more about implementing Wayfound's APIs here.

For more information about connecting agents to Wayfound in order to leverage the API see here:

Connecting Agents

Creating and Configuring Supervisor Agents

Examples for creating supervisor agents and setting their role, goal, and guidelines through the Wayfound public v2 API.

Authentication

All requests use a Bearer token in the Authorization header. The token is a Wayfound API key (a UUID), created under Settings → Connections.

Authorization: Bearer 550e8400-e29b-41d4-a716-446655440000
Content-Type: application/json

Notes:

  • The key must be UUID-format or you get 401 Unauthorized: Invalid API key.

  • MCP-type keys are rejected. Use a standard API key.

  • The key scopes every request to its organization automatically.

Fields

API field
Type
Required
Notes

name

string

yes

Display name of the agent.

role

string

no

Who the agent is / its persona. Stored as the description.

goal

string

no

What the agent is trying to accomplish.

guidelines

object[]

no

Rules the supervisor evaluates sessions against (see below).

Guideline Object

Field
Type
Required
Notes

type

string

yes

One of the guideline types below.

content

string

yes

The rule text. Cannot be empty / whitespace-only.

priority

string

yes

"medium" or "high".

context

string

no

Optional extra context for the rule. Defaults to "".

Valid Types

type

Meaning

prohibitedAction

Prohibited actions

prohibitedWords

Prohibited words

preferredVoice

Preferred voice/tone

formatting

Formatting rules

security

Security rules

bestPractices

Best practices

aiDisclosure

AI disclosure

otherEvaluation

Other evaluation

Valid priority values: "medium" or "high".

1. Create a supervisor agent (role + goal + guidelines)

POST /api/v2/agents

Response — 200 OK

id is the agent's UUID — use it for all subsequent calls.

Minimal create (name only)

name is the only required field. Role, goal, and guidelines can be added later with a PUT.


2. Update role, goal, or guidelines

PUT /api/v2/agents/{agentId}

Send only the fields you want to change. Each PUT republishes the agent.

Update the goal only:

Replace the full guideline set:

guidelines is replaced wholesale, not merged. Always send the complete list you want the agent to have.

Response — 200 OK

Archiving is exclusive. { "archived": true } (or false) must be sent on its own — combining it with any other field returns 400.

3. Read agents back

List all agents:

Get one agent (add ?detail=full for sections/directives):

Response (shape):

Note that on read, priority comes back as "medium"/"high".

Validation & error reference

Status
Body
Cause

400

{ "error": "Missing name field" }

name omitted on create.

400

{ "error": "Invalid guideline type: <type>. Valid types are: ..." }

type not in the allowed list.

400

{ "error": "Invalid priority: <priority>. Valid priorities are: medium, high" }

priority not medium/high.

400

{ "error": "Guideline content cannot be empty for <label>..." }

Empty/whitespace content.

400

{ "error": "Agent Id is invalid format" }

Path UUID malformed.

400

{ "error": "Cannot update archived status with other fields" }

archived combined with other fields on PUT.

400

{ "error": "Invalid agent architecture" }

Agent wasn't created via the API (not SDK).

401

{ "message": "No authorization header provided" }

Missing Authorization header.

401

{ "message": "Unauthorized: Invalid API key" }

Bad/non-UUID/MCP-type key.

404

(empty)

Agent not found in your org.


Last updated