Wire Galaxy's brain into your own product: answer generation and knowledge search open outward, and your own systems connect inward — your shipping endpoint, membership system or stock service becomes the agent's hands. The brain is ours; the interface is yours.
Two doors
outward: answer generation (POST /reply) and sourced knowledge search (POST /search) — with your own API key
31 tools
at the agent's fingertips; define your own HTTP endpoint in the panel and yours joins them
One brain
a question arriving over the API travels the same path as the panel: grounded in your knowledge base, through the same brakes
doors that open outward
Your mobile app, your member portal, your own site — send us the customer's question and we return the sourced answer; how you present it is entirely up to you. With the search door you query your knowledge base and list the results in your own screen.
Answer generation
Send the question, receive the agent's answer — grounded in your knowledge base, with sources. Interface, brand, flow: all yours.
Sourced search
Search your knowledge base; results arrive with the article they stand on.
Key-based access
Access is by API key; you create, revoke and rotate keys from the panel.
Endpoints: POST /reply · POST /search — every request reaches only your own workspace's data.
systems that connect inward
When a customer asks "where is my parcel?", the agent needs to look at your shipping system. Define your HTTP endpoint in the panel; the agent calls it mid-conversation and explains the result in the customer's language. Shipping, stock, membership, orders — whatever systems you run.
Defined in the panel
The endpoint's address, what it does, what it expects — one form; no code changes on your side.
Next-generation connections
It also connects to systems speaking the MCP standard: if you run a tool-serving service, the agent uses it through secure delegated access.
Triggered from outside
When something happens in your own system, you notify Galaxy; the matching automation flow starts on its own.
Every call is on record: which tool, in which conversation, at what time — it sits in the audit log.
security
Every outward surface follows the same discipline: requests are verified by key, each request is locked to your own workspace, and every notification arriving from an external system passes signature verification. The agent's brakes work identically over the API — a claim without a source doesn't leave through the API either.
Workspace lock
Each key is bound to a single workspace; no request can ever reach another customer's data.
Signed messaging
Every notification from an external system passes signature verification; unsigned requests are not processed.
Brakes intact
Forbidden topics, human-approval steps, the source requirement — whatever holds in the panel holds over the API.
You define it, you remove it; no endpoint you haven't defined is ever called.
Yes. The answer door uses the same brain as the panel agent: grounded in your knowledge base, showing sources, stopping on forbidden topics, handing over to a human when needed.
For the answer and search doors, any developer who can make a simple request is enough. Connecting your own system as a tool is a single form in the panel. In your setup week we make the first connection together.
Revoke it instantly from the panel and issue a new one. Since every key is locked to your own workspace, it could never reach another customer's data anyway.
No. The chat box on your website goes in with a single line of code and needs no API at all. The API is for drawing your own interface or wiring your own systems into the agent.
We handle the setup in your first week; we build your first connection together, with example requests.