AnswerLink
Home/03 — Platform

API & Integrations

The Company Brain, outside AnswerLink.

Everything the Brain knows and everything the hub publishes, readable over one API — so your website, your CRM, your internal tools and your own agents can stand on the same confirmed records.

Confirmed records onlyThe API serves what you approved — the same gate the writing obeys.
Answers where you need themRender hub answers inside your main site, your app, or your sales deck.
Events, outwardA captured lead or a published answer can notify your CRM the moment it happens.

You spent the effort confirming what is true about your company. It should work everywhere.

01Reading

One endpoint for what your company knows

Records, answers, themes and figures, each behind a clean endpoint with the same shape. A record arrives with its status and its source — the confirmation trail travels with the data, so a consumer can be as strict as the writing is.

  • Records carry status and source, always
  • Answers arrive render-ready or as structured blocks
  • Scoped keys: read-only by default, per-module when you want it
02Connecting

Leads land where your team already works

A lead captured on the hub can arrive in your CRM with its full context — page, question, answers given — while a webhook tells your tools an answer went live. The hub becomes a source system instead of another silo.

  • Webhooks for leads, publishes and record changes
  • CRM sync with the conversation context attached
  • Exports that keep the categories separated
03Building

Your own agents, on your own facts

Teams are building internal assistants. Point yours at the Brain and it answers from the same confirmed records your public agent uses — one source of truth for what the company knows, however many surfaces speak for it.

  • The same grounding rule your public agent obeys
  • Records as clean input for internal tooling
  • One correction updates every consumer at once
Start to finish

How it actually goes

01Create a keyScoped, read-only by default.
02Read the BrainRecords, answers, themes, figures.
03Wire the eventsLeads and publishes, pushed to your tools.
04Build on itYour surfaces, standing on confirmed records.
Straight answers

What people ask about this

Does the API expose unconfirmed material?

Not by default. The API serves confirmed records, the same as the writing — a proposed record that nobody approved stays internal. If you want proposals too, that is an explicit scope on the key, clearly labelled.

What happens to API consumers when I correct a record?

They get the correction on their next read, and a webhook can tell them the moment it happens. That is the argument for one Brain: fix a fact once, and every surface that speaks for the company follows.

Is this for developers only?

The API is. The integrations are not — CRM sync and webhooks are configured from the interface. The endpoint exists so the things you build later are never limited by what we thought of first.

Every question people ask us

See your own Brain, connected before you decide anything.

The scan is free and takes about four minutes. What comes back is your company, structured — not a demo of someone else’s.

Scan my website