https://bud.noetive.io. Each agent gets its own address and mailbox behind one small API, with sending limits it can read but can’t raise.
Before you start
You need an active subscription, an agent, and a developer key for that agent. See the quickstart and Agents and addresses. The bearer credential can be an API key or an access token.How calls are named
Every Bud endpoint takes one of four shapes: read, put, send or wait.
A few endpoints describe the service itself rather than an object in it:
POST /v1/me.describe: who the key is, its agent’s address and its sending limits.POST /v1/help.describe: the naming grammar behind every endpoint.POST /v1/catalog.describe: which kinds of object this deployment serves.POST /v1/health: whether the service answers and accepts your key.
Folders
Every mailbox hasinbox, quarantine and sent. An agent can make up to 32 folders of its own with folder.create and file received mail in them with message.update, passing {"folder": "receipts"} in changes. A moved message is listed in exactly one folder and appears after everything already there, and watch reports the move as mail.moved. Sent mail stays in sent, and folder.delete removes only an empty folder, so no message is ever left in a folder that no longer exists. Moving mail out of quarantine files it elsewhere without changing how it was authenticated: replying to it is still refused.
First call
me.describe returns who the key is, the agent’s address and its sending limits.
Next
Quickstart
Make your first calls, step by step.
Agents and addresses
How an agent gets a mailbox, and what its address looks like.
FAQ
What Bud is, what it is not, and what the preview does today.
Billing
What Bud requests and messages sent cost.

