AI agentsfor your product.One recipefor every customer.

Give every customer an agent inside your app. Sokko runs the agents; you control the instructions, tools and memory.

The agent layer for your product.

Agent as a Service gives software teams an API to create and run agents for their customers. Keep your own interface while Sokko provides the workspaces, agent runtime, connected tools and shared memory.

A workspace for every customer.

Create each customer’s workspace under your partner account. Give it the agents, tools and memory that fit their work.

  • Choose the agents they need.
  • Assign skills and MCP server access.
  • Keep their shared context in their workspace.

Example customer setups

  • Acme

    Support agent · order policies

  • Bloom

    Writing agent · brand voice

  • Fern & Oak

    Operations agent · team knowledge

Define it once. Reuse the recipe.

A recipe is the blueprint for an agent. It keeps the setup consistent while each customer gets their own working agent.

Choose the ingredients

Set the model, instructions, skills, MCP servers and starting memory in one bundle.

Keep track of changes

Version the recipe so you know which setup you’re using to create agents.

Test before rollout

Run the recipe’s test command before using that version for more customers.

Support agent recipe

v1.2
Model
Your chosen model
Instructions
Acme support guidelines
Skills
Order questions, reply drafting
MCP servers
Customer knowledge base
Seed memory
Return policy, brand tone

A test command belongs to each recipe.

Useful agents need more than a prompt.

Give agents the capabilities to do the work and the customer context to do it well.

Connect the tools they need.

Add task-specific skills and register MCP servers. Then assign access to the agents that need them.

Skill
Answer order questions
MCP server
Store knowledge base
Assigned to
Support agent

Register a tool once, then choose which agents can use it.

Keep customer context in reach.

Read and write the workspace’s shared memory from your product. Its agents can use the same facts, preferences and instructions.

Acme’s shared memory

Tone: concise and friendly Returns: within 30 days Escalations: ask the support team

The shared context belongs to that customer’s workspace.

From your app to a useful answer.

Use the partner API from your backend. Keep the onboarding, interface and customer relationship in your product.

  1. Step 1: Set up a customer

    Create a workspace under your partner account. Add the customer’s starting context.

  2. Step 2: Create their agent

    Use a versioned recipe, then assign the skills and MCP servers that customer needs.

  3. Step 3: Bring the answers back

    Send the request and stream the answer into your app. Read or update shared memory through the API.

You own the product experience

Your interface, customer onboarding and agent instructions.

Sokko provides the agent layer

Managed agents, customer workspaces, tools, shared memory and streamed responses.

A few things to know.

Have a use case in mind? Bring it to the call and we’ll work through the setup with you.

Book a call

Can I use my own interface?

Yes. Your backend calls the partner API, and your app displays the agent’s streamed response. You keep the onboarding and customer experience in your product.

How is a recipe different from an agent?

A recipe defines the model, instructions, skills, MCP servers and seed memory. An agent is a running instance of that setup in a customer’s workspace. Recipes are versioned and include a test command.

Can each customer have different tools and memory?

Yes. Reuse the same recipe, then give each customer’s agents the tool access and workspace context they need. Your product can read and write that shared memory through the API.

How does pricing work?

We’ll discuss your expected number of customers, agent workloads and model usage on the call, then work through a plan for your product.

Is the partner API available today?

The partner API is in development. Book a call to discuss your use case, integration needs and rollout.

Let’s put agents in your product.

Show us what you’re building. We’ll map the first use case, customer workspace setup and integration needs.

Book a call

Partner API in development.