Canonical page: https://tellenze.com/developers

Developers · Build with the shared work record

# Connect the request. Keep the context.

Bring outside requests into clear work. Let a connected agent make a useful, reviewed contribution. Start with a complete recipe, then use the reference for the details.

[Choose a recipe](#recipes)[API or MCP?](#choose-connection)

Supported product paths with fictional examples. Your workspace’s access, configuration and review rules still apply.

Small integrations. Useful outcomes.

App API

External request

Defined, attributed task

[Follow the intake recipe](https://tellenze.com/developers/recipes/external-request-to-task)

MCP

Authorized task context

Reviewed change → Fresh check

[Follow the agent recipe](https://tellenze.com/developers/recipes/reviewed-agent-update)

Choose your connection

## The right path for the job.

Both paths work within current permissions and keep contributions attributable. Choose by what your integration needs to do.

App API · Your server integration

### A request arrives. Give it a work record.

Use ordinary HTTP requests when a support system or another service needs to read granted projects, create work or update supported definition fields.

ConnectionA member-owned App token with explicit project and operation grants.

Good starting pointSource request → Defined task → Safe retry → Read back.

BoundaryProjects and Focus are read-only. Task definition updates do not change workflow or ship work.

[Read the App API overview](https://tellenze.com/developers/api)

MCP · Your connected agent

### A contribution needs the work’s context.

Use a compatible agent client when the contribution needs the task, its sources and current guidance, then a precise supported change.

ConnectionOAuth through the member’s workspace and selected machine profile.

Good starting pointRead context → Propose → Human review → Save → Verify.

BoundaryTool availability and access still apply. A proposed edit does not authorize publication or completion.

[Read the MCP overview](https://tellenze.com/developers/mcp)

Two complete recipes

## See the whole small workflow.

Each recipe includes setup, a fictional input, exact requests, expected results, verification and recovery. Copy individual examples or take the full Markdown pack.

App API01

### [Turn an external request into defined work](https://tellenze.com/developers/recipes/external-request-to-task)

Bring a support report into one attributed task, keep its external identity and verify the saved definition.

- Check existing work

- Define and create once

- Read back and retain the mapping

You leave withOne work item with the source, a clear boundary, acceptance checks and a saved external-to-work mapping.

[Download the recipe](https://tellenze.com/developers/recipes/external-request-to-task/download)

MCP02

### [Make a reviewed agent update and verify it](https://tellenze.com/developers/recipes/reviewed-agent-update)

Read the authorized task and pinned guidance, review a precise proposal, then save and check one versioned definition change.

- Read context and pinned guidance

- Review and save one exact change

- Verify the fresh saved result

You leave withThe approved acceptance criteria are saved once, with the original task’s scope and workflow state preserved.

[Download the recipe](https://tellenze.com/developers/recipes/reviewed-agent-update/download)

Before the first write

## Make the connection clear.

### Choose the right access.

Confirm the workspace and responsible member. Grant only the projects and operations the integration needs. Keep credentials in a secret store.

### Read the required guidance.

Retrieve current Required Context before supported changes. Complete pinned reading and delivery acknowledgement where required.

### Review, retry and verify.

Keep each logical write’s exact body and key. Use current versions for edits. Review the intended action and check the fresh saved result.

Go to the source

## Keep the reference close.

The recipes show a coherent path. These guides hold the complete setup, capabilities and access rules.

COME TAKE A LOOK

## A little less busy.  A lot more together.

Curious? Join the waitlist and see how we welcome your team.

Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.

[Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.