Bring your scripts in behind a contract.
teleon.dev/docs/lift wraps the scripts, containers and APIs you already have behind versioned contracts, so agents can call them like any other capability.
Lift keeps your code as it is and adds the contract and checks around it.
What it does
Keep what works
Existing scripts, containers and HTTP APIs come in as they are.
Contract on the outside
Lift writes a typed spec for inputs, outputs and checks around each one.
One command
The CLI inspects the source, proposes the contract and runs its checks.
The contract
An import produces a capability spec, a wrapper and a first test report.
capability_task_spec/v1recursive_component_wrapper_engine/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
POST | /lift/v1/inspect | RING-2 | Inspect a source and propose a contract | |
POST | /lift/v1/import | RING-2 | Import with an agreed contract | |
GET | /lift/v1/imports/{id} | RING-2 | Read an import's test report |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/lift.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Contract
- A versioned agreement on the shape of a request and response, so either side can change behind it safely.
- Kleisli wrapper
- A thin layer that wraps a call with one concern, such as clamping inputs or scrubbing secrets, and composes with others.
- Capability card
- A short description of what a component does, its typed inputs and outputs and its license, sized for an agent's context.