Quickstart
Set up a real team in the console, or create your first worker and task from code — both in under five minutes.
Set up a team — no code
- Sign up. Open the console and answer the one question — what you are routing. Your workspace arrives already matching a demo of that shape, so there is something to look at before you have typed anything.
- Describe your work. On Setup, pick the starter closest to your team and adjust it. Skills are what make one person a better fit than another; teams let you address a crew instead of a person.
- Invite your people. From the same page, into a role. Each gets a link that sets their own PIN and drops them straight into the worker portal — where they say what they can do, and go on shift when they are ready. You never type anyone's skills for them unless you want to.
- Bring your backlog. Tasks → Import takes a CSV. It tells you before importing whether anyone can actually take each kind of work — a tag nobody carries is the one mistake that costs you a queue that never drains.
- Watch it route, and ask why. Every match is recorded with the full candidate list, the score each got, and the rule that excluded the rest. Open any task to see who won it, or a queued one to see what is holding it up.
Or drive it from your own code
- Get a sandbox key. Sign up at the console — every new workspace comes with an
sk_test_...key. - Install the SDK.
pip install fivexer
- Run the snippet. Replace
sk_test_...with your key.from fivexer import Fivexer, CreateTask, UpsertWorker client = Fivexer( base_url="https://api.fivexer.com", api_key="sk_test_...", ) client.workers.upsert(UpsertWorker(id="agent_1", tags=["english", "billing"])) task = client.tasks.create(CreateTask(tags=["english", "billing"], priority=90)) print(task.id, task.status) # task_8fk2 queued - Verify a webhook. When the platform matches the task, it posts a signed
task.matchedevent to your endpoint. See the webhooks guide for verification code in every language.
Next: How matching works or try the API in the browser. Want an agent to do it? The MCP server exposes the same operations, including a bulk create for loading a backlog in one call.
Was this page helpful?