Build your first AI employee

Four steps from an empty workspace to a live agent on your website.

1. Create your workspace. Sign up at /register. The organization you name becomes your tenant — every agent, document and record below belongs to it and is never visible to another organization.
2. Add knowledge. Under Knowledge, point Synapta at a website, upload documents, or connect a data source. Content is chunked, embedded and indexed per organization.
3. Build an agent. Under Agents → Deploy Agent, give it a name, a role, and instructions in plain language. Attach the knowledge sources it is allowed to read.
4. Activate and embed. Set the agent to Active, then copy the embed snippet from the agent page onto your site.

An agent is a named role with instructions, a model, and a set of knowledge sources it may draw on. Agents are configured, not coded — the instructions field is prose, and it is the main lever on behaviour.

Each agent has two states. Draft is private to your team and testable from the Testing page. Active is reachable by the public through its widget key.

Use Testing to talk to an agent with the same retrieval path a real visitor gets, before anyone else can reach it.

Knowledge sources are what keep answers grounded. Each source is ingested, split into passages, embedded, and stored against your organization. When an agent answers, the relevant passages are retrieved and passed to the model — so answers cite your material instead of the model's general training.

Sources can be re-synced from the Knowledge page when the underlying content changes. Re-syncing replaces that source's passages; it does not touch other sources.

Business rules constrain what an agent may do — for example, a discount threshold above which it must not commit.

Custom actions let an agent call your systems. An action has a function name, a description telling the agent when to use it, typed parameters, and a webhook URL that receives the call.

Actions can require approval. When one does, the agent raises an action request instead of firing the webhook, and a human approves or rejects it. This is the intended pattern for anything that moves money, sends external mail, or changes a record of record.

Beyond documents, agents can be given structured records — customers, invoices and support tickets — so they can answer questions that knowledge retrieval alone cannot, such as which invoices are overdue.

Ask Your Business on the dashboard queries this layer in natural language for authorized users.

Website widget — available now. Every active agent has a public widget key. Embed it with an iframe:

<iframe
  src="https://synapta.naidvartechnologies.com/widget/YOUR_AGENT_PUBLIC_KEY"
  width="380"
  height="600"
  style="border:none;border-radius:12px;">
</iframe>

The key is a UUID that identifies the agent publicly. It carries no account access: it can only start and continue conversations with that one agent, and requests are rate limited per IP.

Members are invited by email and hold one of three roles:

• Owner — full control, including billing and deleting the organization. An organization must always keep at least one Owner; the last one cannot be demoted or removed.
• Admin — manages agents, knowledge, logic and members.
• Member — day-to-day use of the workspace.

Ownership is never granted by invitation — an existing Owner has to promote someone deliberately.

Everything the dashboard does runs through the same public REST API, so anything you can do in the UI you can automate.

Base URL: https://synapta.naidvartechnologies.com/api

Authenticate once to get a bearer token, then send it on every subsequent request:

curl -X POST https://synapta.naidvartechnologies.com/api/login \
  -H 'Content-Type: application/json' \
  -d '{"email":"[email protected]","password":"..."}'

# → { "token": "1|abc...", "user": { ... } }

curl https://synapta.naidvartechnologies.com/api/agents \
  -H 'Authorization: Bearer 1|abc...'

Commonly used endpoints:

The public widget endpoints (/widget/agents/{publicKey}) need no token and are rate limited per IP.