Skip to content

Artific Core

Artific Core is a platform for building solutions with language models for your customers. You define which agents exist, what they know and what they may do, kept apart per customer. Your application calls that through one API, and in the console you manage access and see usage, audit events and traces.

This guide is written for those who build on Core: the developer who calls the API and the administrator who uses the console. When you build a product of your own with its own interface, in which your customers never see the console, start at Building a platform on Core.

The building blocks

  • Organisations: every customer has a closed-off space of its own with its own administrators, keys, data and caps.
  • Keys, capabilities and policy: one key per application, and rules that decide which models, tools and data that key reaches.
  • Agents: the AI that reasons and acts: a model, instructions, skills and tools, stored under a name and with versions.
  • Workflows: a business process as steps of agents, tools and people, which Core carries out in the background.
  • Knowledge: what an agent can know: documents in collections, searchable in indexes and knowledge graphs.
  • Memory: what an agent keeps between conversations, and whether it belongs to one person or to the whole organisation.
  • Datastores: structured records that your application and an agent both read and update.
  • Tools and MCP: what an agent can do: APIs, MCP servers, searching the web, running code, handing work to another agent.
  • Structured answers, artifacts and pages: answers as JSON following your schema, files a tool makes, and reports you show in a browser.
  • Models, insight and sharing: which model an agent works with and what it costs, what happened, and how you install one solution at several customers.

The Core model shows how these building blocks form a solution together.

Three ways in

Understand. Read The Core model and then Organisations and customers. The pages under Understanding Core each explain one building block: what it is, when you use it and how it relates to the rest.

Build. Send your first call or open the console. Then follow the tutorials: seven walkthroughs, from a first agent to one solution for several customers. Build has one page per task, for the API and for the console:

Look up. The API reference shows every route and lets you try it out in your browser. Model calls go through POST /responses and follow the Responses format; Requests describes Core's conventions for those and for every other route. Capabilities lists the features a key can switch on.