What Ayven does

Ayven is an AI coordinator for teams that works inside Slack and Microsoft Teams. It takes an ask, gives it an owner and a deadline, chases the people who owe something until they answer, verifies the work actually happened, and reports back — the coordination work a person would otherwise do by hand. It also runs research, files tickets, and writes documents. Every change to a connected system is proposed to a human and executed only after approval. Ayven is built by Alknoma Ltd, a company registered in England and Wales.

Ayven at a glance

The loop Ayven runs

Ayven's core behaviour is one loop, run continuously on every ask it is given. Most of what follows is that loop applied to a different kind of work.

What Ayven can do

Six capability areas, each documented in full at the link on its heading.

Chasing and verified completion

Ayven owns the follow-up loop: who owes what, when it was due, and whether it actually got done.

• Asks each owner individually and keeps asking, rather than pinging the channel
• Holds owner, deadline, chasing, and digests natively — before any tracker is connected
• With a tracker connected, ticket-linked work closes only when the tracker shows the change
• Blockers get an owner and a give-up date instead of sitting in a thread

Research with cited sources

Ayven searches the team's connected documents and the open web in parallel, then writes up the answer with every source attributed.

• Vector-based semantic search over the connected document workspace — meaning, not keywords
• Web search with source verification
• Findings carry cited sources, confidence levels, and follow-up questions
• Three scopes: internal (your docs only), external (web only), or hybrid (the default)

Tickets filed from conversations

A thread becomes a real ticket in Jira, YouTrack, or Asana, with the context that produced it and an owner attached.

• Duplicate detection by semantic similarity before anything is filed, including across projects
• The full lifecycle: assign, change state, comment, set sprint and labels, link related tickets
• Assignee suggestions drawn from who has actually worked on the subject
• Every ticket is previewed and editable before it lands; Ayven learns from the edits

Documents written and indexed

Ayven plans a document's structure, writes it section by section, and indexes it so later research can find it.

• Content-aware section planning with per-section depth: brief, standard, or comprehensive
• Create, update, move, share, and delete — updates arrive as a diff to approve
• Automatic vector embedding and metadata extraction on everything it writes
• Documents land in the team's connected storage, organised into folders

Missions — work that outlives one conversation

Long-running concerns are held open for weeks or months and re-checked on their own schedule, instead of being forgotten when the chat closes.

• Confidence-based behaviour: high confidence acts, medium proposes and waits, low drafts and asks
• When blocked, the mission pauses and routes a specific question to a specific person
• The answer feeds back in and work resumes automatically
• Lifecycle is open, paused, or closed — and a closed mission reopens if conditions change

Team intelligence

Ayven learns who knows what and what each channel is for, so asks reach the person who can actually answer them.

• User profiles: expertise areas and communication patterns, each fact confidence-scored
• Channel profiles: real discussion patterns, key participants, content types
• Older facts are weighted down as they age, so the picture tracks the team as it changes
• Only messages in channels Ayven was invited to are analysed — DMs and private channels are excluded

What using Ayven is actually like

Ayven has one rule and 5 surfaces. The rule is that it asks before it acts; the surfaces are where the asking and the answering happen.

The chat channel

Ayven is mentioned like a colleague in Slack or Microsoft Teams. Requests are made in plain language, and its questions come back as ordinary messages that a plain reply resolves.

Why it matters: No new tool to open and no one to train. Adoption does not depend on the team changing where it works, which is where most coordination tools fail.

The approval gate

Anything Ayven wants to change in a connected system arrives first as a proposal: the exact ticket, the document diff, the message it intends to send. You approve, edit, or reject it.

Why it matters: The agent can be given real write access without the team losing control of what enters their systems. Being wrong costs a rejection, not a cleanup.

The web app

An inbox of pending approvals and input requests, the mission register, a dashboard of what is in flight, and the integrations and settings screens.

Why it matters: One place to see everything the agent is holding, so nothing depends on remembering a thread from last Tuesday.

The audit log

Every approval, rejection, response to an input request, and settings change is recorded with who did it and when.

Why it matters: The record of what an autonomous system was allowed to do is a prerequisite for letting it near production systems at all.

Agent settings

Messaging tone, channel etiquette, document writing style, ticket writing format, automated routines, and which operation types may skip the approval gate.

Why it matters: The agent writes in the team's register rather than a generic one, and the approval burden can be relaxed for the classes of action a team has stopped wanting to review.

The Ayven HTTP API

The API is not a separate subsystem — it is one more messaging platform alongside Slack and Teams. A message sent over HTTP runs through the same pipeline as a message sent in a channel, and everything Ayven can do in a channel it can do here.

The contract in full is in the API reference; what follows is the shape of it.

Base URL and authentication

https://platform-gateway-3124114101.europe-west1.run.app/api/v1/api-channel

Authorization: Bearer ak_<keyId>_<secret>

Any workspace member can mint their own key from the web app. A key acts as the person who created it and reaches that person's agent; listing and revoking are per-issuer. Each key carries its own per-minute rate limit.

Endpoints

Send the agent a message and get its reply. Pass a session_id from an earlier response to continue a conversation with its history intact, like replying in a thread; omit it to start a new one.

Read a conversation's durable transcript. This is how the reply to a long-running turn is retrieved.

Example

curl -X POST https://platform-gateway-3124114101.europe-west1.run.app/api/v1/api-channel/messages \
  -H "Authorization: Bearer ak_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "What is the status of the Q3 board update?"}'

{
  "session_id": "3f9c2a1b8d",
  "status": "completed",
  "reply": "The Q3 board update is with finance for sign-off…"
}

Reply statuses

A turn that outruns the request's wait ceiling returns status "processing" with no reply. Nothing is lost: the run continues, the reply lands on the durable transcript, and the GET endpoint retrieves it.

Errors

What Ayven does not do

• Ayven does not act on connected systems without approval. Writes to trackers, documents, and outbound messages are proposed first, unless a team has explicitly auto-approved that class of operation.
• Ayven does not read direct messages or private channels. Only channels it has been invited to are analysed.
• Ayven does not replace your tracker. It runs the coordination loop on top of the Jira, YouTrack, or Asana board you already have.
• Ayven is not a chatbot that forgets. Missions and tracked items persist across conversations, and history is carried per thread and per API session.
• Your data is not used to train models.

Where to go next

This page is also published as plain markdown at /llms-full.txt, with a site map at /llms.txt.