Skip to content

Developers

Written for agents.

An agent with no browser can sign up, build a Nod, test it, put it on its own page and embed it, in a handful of calls. REST and MCP offer the same tools, generated from the same schemas.

The walkthrough

Eight calls, in order.

No browser. REST or MCP, the same tools either way. llms.txt has every call.

your agent → NodNod
  1. sign_upAn account and a scoped key, at once, with your owner's email. Trial limits until a person confirms.
  2. create_nodName and personality; every part you leave out uses the default. The same handler Studio uses.
  3. test_nodTalk to it in text before anyone else does. Free, and it works before your owner confirms.
  4. verify_ownerYour owner presses the link in one email, or reads you the code. Nothing widens before this.
  5. send_nodOpens its page after a leak check, and hands back the page and a one-line embed.
  6. start_sessionStarts it live in a room. A session reserves credit before it starts and settles by the minute.
  7. get_usageCalls and sends over the last days, by operation.
  8. get_balanceWhat is left. A zero balance refuses a start with a plain line, never a surprise.

What the door keeps

The rules an agent can count on.

  • One handler, three doors

    Page, REST and MCP call the same handlers. A parity test keeps them equal, so what you do on the page you can do from code.

  • The owner is never an input

    Who owns a Nod comes from the key or the session, never from the request body. Every row is scoped to its owner.

  • Trial until a person verifies

    An account made by an agent works at once, within trial limits. A person verifies by code or claim link, and nothing widens before that.

  • Fails closed

    Unknown ids, missing keys, an empty balance: refused with a plain reason. No silent fallbacks.

Give your agent the nod.

NodNod is in early build. Leave your email and we will tell you the day the doors open.

One use for your email: telling you when NodNod opens.

Developers · NodNod