Korelos

Your First AI Agent in Under 5 Minutes

Written by

Korelos Team

in

Tutorial

Your First AI Agent in Under 5 Minutes

Korelos Team · 2026 3 5 · 4 min read

One of the things we care most about at Korelos is time-to-first-working-agent. If you have to spend an afternoon setting things up before seeing anything useful, we haven’t done our job. Here’s how fast the real experience is.

Step 1: Create your agent

Log into the Korelos Studio portal and click New Agent. Give it a name and write your system prompt in plain English. This is where you define what the agent does, how it responds, and what boundaries it operates within.

You are a customer support agent for Acme Corp. 
You help users with billing questions, order status, and returns.
Always be concise. If you can't resolve something, escalate to a human.
When looking up orders, always verify the user's email first.

That’s it. No YAML, no schemas, no configuration files.

Step 2: Connect your tools

Tools are what give an agent the ability to do things beyond answering questions. In the Studio portal, you can connect tools from our library (including database lookups, HTTP requests, Slack, email, and more) or define custom tools with a simple JSON schema.

For our support agent, we’d add an order_lookup tool and a create_refund tool. Each tool has a name, a description (which the model uses to decide when to call it), and a schema for the parameters.

Step 3: Deploy and call the API

Click Deploy. Korelos generates an endpoint for your agent. From that point on, you interact with it over a standard REST API:

POST /v1/agents/{agent_id}/run
{
  "session_id": "user_12345",
  "message": "Hi, I need help tracking my order #4821"
}

The platform handles the conversation state, tool execution, retries, and logging. Your application just sends messages and receives responses.

What you get for free

  • Persistent memory across sessions (scoped per user or globally)
  • Automatic retry logic for tool failures
  • Full execution logs in the Studio dashboard
  • Versioned deployments so you can roll back instantly
  • Rate limiting and auth built in

None of that required any extra configuration. It’s there by default because those are the things every production agent needs.

More posts