Skip to main content
Pushing knowledge is one half of the API. The other half authors the agents themselves: everything the dashboard configures is config-as-data you can write over the API — no field is dashboard-only.

​
What you can author

  • Agents — provision a new agent from a starter, tune its widget settings, rename it, and take it live or pause it (PATCH /agents/{slug} with status).
  • Catalog — the services an agent offers, the fit criteria it qualifies against, and the voice it speaks in.
  • Identities — the personas agents act as for outward operations: sender name, address, reply-to, signature.
  • Flows — the conversation itself: its phases and the answers each one captures.
  • Prompt templates — versioned prompt bodies per kind: author a new version, roll back to any prior one.
  • Deliverable templates — the wrap-up document’s A/B variants: sections and guidance per variant.
  • Knowledge facts — triage the atomic knowledge your sources yielded: review, edit, archive-as-suppression, tier pinning, per-agent scoping.
  • Drafting — let pepline propose that catalog from what your agents already know, and accept what fits.
And one surface is read-only by design: conversations. List an agent’s conversations and retrieve any one in full — transcript (with each reply’s grounding), captured answers, lead assessment, and the delivered document — for lead research and QA. Writes stay the widget’s alone: a conversation is the visitor’s record. The same surface serves three callers: pepline’s own concierge onboarding, the pepline MCP server, and your own tooling.

​
Conventions that hold everywhere

  • Declarative activation. Many resources take an agents array of slugs that is a full replacement set — the resource ends up offered by (or active for) exactly the agents you list. Omit it to leave activations untouched; send [] to deactivate everywhere.
  • Archive, never delete. Nothing is destroyed. Archiving removes a resource from an agent’s world while keeping its history; restoring brings it back. (DELETE on a source answers 405 and points you at the archive verb.)
  • Flows trial-compile. Every write that touches a flow is compiled in the same transaction before it commits. An illegal change — over the slot budget, a reserved key, moving the closing phase — rolls back with 422 flow_invalid. You cannot author a broken agent.
Everything here is authenticated the same way as the rest of the API — see Authentication.