Yekar.AI
Login

Put it to work

Start agents through an API trigger

Make a published agent part of your own application or service.

Talk to usRead the docs
Captured from the product Demo workspace
Call a published agent from your own product or backend.

What this changes for your team.

Machine callers authenticate with a dedicated credential and POST a typed request to an API trigger. Authorization is rechecked at fire time, so holding a credential never widens the caller beyond its owner's trigger access. Where you want several agents behind one published entry point, Apps do that as well and are enabled on request.

How it works in practice.

  1. 01

    Publish the agent and subscribe it to an API trigger.

  2. 02

    Mint the matching machine credential and store it only in your backend.

  3. 03

    POST the input, retain the returned run identifier, and inspect or receive completion through the API surface.

What you can plan around.

The behaviour you can design against, stated concretely.

Where an App is enabled, its credentials reach only the agents attached to that published App.

Personal trigger keys act with their owner's permissions, rechecked on each fire.

Authorization-shaped misses return a uniform not-found response rather than revealing inaccessible resources.

Complete the operating path

View all capabilities
Put it to workUse your agents from Claude Code, Cursor and VS Code

Put the agents your team has built inside the coding assistants your team already works in.

Put it to workRun recurring work on the business's clock

Express recurring work once and have it evaluated against the timezone the business uses.

Run it reliablyNever lose track of accepted work

Give every accepted unit of work a durable identity and history before execution begins.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Talk to us