THE CORE PLATFORM

Your product.
Agentic by design.

Connect agents to the app you already have. Core brings execution, knowledge, workflows, and embedded UI together, so you can focus on the experience your customers use.

ALREADY CONNECTED

One platform.
The whole agent experience.

Define the work, connect your systems, and put the result in front of people. The pieces work together from the start.

01 / AGENT EXECUTION

You define the work.
Core runs the agent.

Configure the goal, model, tools, and knowledge. Core handles model calls, context, tool use, and refinement, with reusable patterns for research, creation, and specialist collaboration.

See a team of agents at work
CORE RUNTIME
  1. Start the work01
  2. Run the agent02
  3. Use your tools03
  4. Refine the result04
  5. Deliver to your app05
Illustrative execution path
02 / EVENTS & CONNECTIONS

Keep every system in step.

Start from events or schedules. Stream progress to your app, wait for external signals, and deliver notifications through signed webhooks or your AWS SQS queue.

03 / CONNECTED KNOWLEDGE

Give every agent useful context.

Create collections around your products, customers, or processes. Core manages indexing, embeddings, and search so agents can find relevant information and reference its sources.

Watch data become knowledge
04 / VISIBILITY

See the work as it happens.

Follow parallel tasks, see why a branch was chosen, and pick up where external work left off. Keep progress, results, and usage in view.

05 / MODEL CONTROL

Your models. Your boundaries.

Bring your provider credentials. Choose a supported model, reasoning level, and budget for each agent, with AI provider charges kept separate from platform usage.

Provider
Your connected account
Reasoning
Set per agent
Run budget
You set the limit
EMBEDDED UI

Make the experience
part of your product.

Bring agents into the product your users already love. Compose React components and headless hooks for output, progress, approvals, and finished work.

Try the components. Review a draft, request changes, and save a result.

your-app.com / workspaceYOUR PRODUCT
Projects Autumn launch
In review

Workspace launch brief

JDJamie Davis·Version 1

The opportunity

Introduce the new workspace to customer teams through a focused pilot, supported by a clear launch narrative and a practical adoption plan.

Who it’s for

Customer teams coordinating work across multiple tools.

Launch approach

Invite a focused pilot group
Capture adoption signals and feedback
Refine before wider rollout
Launch assistant Connected to your workspace
EMBEDDED
01Agent panel
Turn our product notes into a launch brief.

I’ll use your product notes, customer insights, and brand guide to build a brief your team can review.

Product notesCustomer insightsBrand guide
LET’S PUT IT TO WORK

A familiar conversation. Connected to your knowledge and tools.

Interactive preview with sample content. No connected services or customer data.

Compose your experience.

Use React components for the essentials. Reach for headless hooks when you want full control of the interface.

Make it feel like you.

Bring agent capabilities into your layouts, your design system, and the moments that matter in your product.

Keep access in your hands.

Your backend authenticates users and grants scoped access. No separate platform login for your customers.

BUILDING WITH CORE

What Core handles.
What your team supplies.

Core provides the agent infrastructure. Your team connects it to your product’s rules, systems, and users.

Responsibilities when integrating Core into your application
Core handlesYour team supplies
Agent execution & workflow coordination

Run agents, coordinate steps, and resume work after input or approval.

Domain logic & business tools

Define objectives, implement business tools, and choose which actions need review.

Progress, input, approval & result interfaces

React hooks and components show progress, collect responses, and present results.

The surrounding product experience

Design your pages, style the components, and decide where agents fit into the user journey.

Knowledge indexing & retrieval

Index supplied content and retrieve relevant material within configured access.

Data selection & access policy

Choose source material, keep it current, and configure who and which agents may use it.

Integration mechanisms & scoped context

Provide the server SDK, scoped client sessions, and events; enforce Core’s configured permissions.

Authentication & business-system authorization

Authenticate your users, establish their scope, and enforce permissions in your business APIs.

Your server creates a scoped client session after sign-in. Your Core API key stays on the server.

FOR DEVELOPERS

A small integration.
A bigger product.

Add agentic capabilities to your product with an execution engine already built in. Configure agents and workflows, start work through an API, and receive progress and results in your app.

Configure the agent. We run the loop.

Set the objective and instructions, choose a model, and connect tools and knowledge. The platform manages model calls, tool execution, and the steps needed to produce the result.

Events that reach your systems.

Route progress and completion through signed webhooks or your AWS SQS queue, with retries and delivery history.

Keep work moving across boundaries.

Call your tools, wait for an external task, then resume with its result. Your app can follow every step and fetch the output.

TYPESCRIPT SDKTS
import { Jwtson } from '@jwtson/sdk';// Reads JWTSON_API_URL and JWTSON_TOKENconst jwtson = new Jwtson();// Creates it, publishes a change, or does nothingconst agent = await jwtson.agents.ensure({  name: 'Summarizer',  instructions: 'Summarize the text in one sentence.',});const run = await agent.start('A long article...');for await (const text of run.textStream()) {  process.stdout.write(text);}
COMMON QUESTIONS

Good questions.
Clear answers.

01Do we need to build our own agent engine?

No. Agentic processing is built into the platform. You configure objectives, instructions, models, tools, and knowledge. The platform provides the execution loop, context handling, and reusable patterns for research, creation, review, and collaboration. Your team connects the business systems and defines the work, without building agentic processing from scratch.

02What can I build with it?

Research that brings together several specialists. Onboarding that adapts to each customer. Campaigns that improve through feedback. Document studio turns connected knowledge into a finished document. Connect agents, tools, and everyday business steps into a workflow built around the outcome you want.

03Can agents create documents from our knowledge?

Yes. Document studio shows the whole process: search your knowledge by meaning with embeddings, gather the relevant material, plan the structure, and write a draft. Edit or refine the document, then save the version you want. Your application can receive the completion event and retrieve the finished work.

04Can a workflow do more than follow a straight line?

Yes. Run specialists in parallel, combine their results, choose a branch based on new information, or refine an output through a bounded feedback loop. Work can also wait for input or an external event and continue from that point. Use agents where reasoning helps and ordinary steps where the path is clear.

05How does it connect to our apps and systems?

Start workflows through APIs, incoming events, or schedules. Connect tools to read data and take action in your systems. Stream progress into your interface and route notifications through signed webhooks or your AWS SQS queue. Your own integrations can use those events to update a CRM, send an email, or trigger the next process.

06Can we embed agents directly in our web app?

Yes. React components and headless hooks bring agent output, live progress, input and approval forms, and finished results into your product. Compose the experience around your design system. Your backend authenticates users and grants scoped access, so people can work with agents inside your app without a separate platform login.

07Can we use our own model credentials?

Yes. Bring your provider accounts and choose a supported model, reasoning level, and budget for each agent. A research specialist and a writing agent can use different configurations. AI provider charges remain separate from platform usage.

08Where do people fit into the process?

Where you want them. Let a workflow run from start to finish, ask someone for missing information, or add a review before a particular action. Input and review are building blocks you choose for the work, and a waiting workflow can continue when the response arrives.

09Does this replace our existing application?

It fits behind your existing product. Your application keeps its interface and business records while agents handle multi-step work through your tools. APIs, progress streams, and events connect the experience, so your users can stay in the app they already know.

BUILD THE NEXT CHAPTER

Build the app
you wish you had.

Start with one useful agent. Give your users a new way to get work done.