Tools-as-a-Service

Your platform, agent-ready.
Without rebuilding a thing.

Pontil scans your existing APIs and generates the tools your agents need. We keep them current as the product changes. We run them as the authenticated user.

THE PROBLEM

The model isn't the blocker. Reach is.

SaaS products spent years being built for the UI. The APIs kept up with some of it. Most of it, they didn't. Now agents need to act on the same surface — and can't get to it. This isn't a model problem. It's an access problem. The agent can reason about what to do. It can't do the thing.

The three cards on the table

01

Rewrite the API layer

Two-to-five-year project. Competes with the product roadmap. Doesn't get funded.

rejected
02

Buy an iPaaS

Works for one. Doesn't compound across a portfolio. Maintenance burden outgrows the value.

doesn't scale
03

Use an agent framework

Covers the top 20% of apps. Leaves the long tail uncovered. Hands your access story to someone else.

strategic risk
Pontil product components shown in mobile view
THE solution

What if there was a fourth option?

04

Pontil

Pontil scans your existing APIs and generates the tools your agents need. We keep them current as the product changes. We run them as the authenticated user.

SHIP IT

Want to talk through the specifics for your environment?

how pontil works

One platform. Three components that work together.

01 — Tool generation and maintenance

Scan the codebase. Generate tools from APIs that already exist.

Connector generation reads your existing surface and produces structured actions. Tool composition turns those actions into workflows a business user would recognise. Humans approve what gets exposed.

Diagram of Pontil scanning a codebase to discover existing APIs
02 — Tool runtime

A managed execution layer. Deterministic, observable, scoped to the user.

Pontil runs the tools. Retries, timeouts, rate limits, and the auth lifecycle are handled at the runtime layer — not pushed onto your agent or your product.

Diagram of Pontil's managed runtime executing tool calls as the authenticated user
03 — Agent SDK

The interface between your agents and the runtime.

Agents discover the tools available to the current user, fetch current definitions at call time, and invoke them — scoped at the call site. No redeploy to ship a tool update.

Diagram of Pontil's Agent SDK as the interface between agents and the runtime
use cases

What does your platform look like?

01
Illustration of a vertical SaaS use case for Pontil

Vertical SaaS

Your customers live in one industry and your product runs deep workflows that exist nowhere else. The UI is rich. The API was built for the integrations that mattered most. Customers are asking about agents, and the API surface doesn't reach what the UI does. Tools are generated from the codebase, not from the published API. Agents reach the workflows your UI runs.

02
Illustration of an internal platform use case for Pontil

Internal platforms

You run dozens of internal platforms — some ancient, some new, none built for agents. Your teams want internal agents and copilots that can actually do things. The platforms behind those workflows are sprawling, undocumented, and impossible to rewrite at portfolio scale. The scanner runs against each app where it lives, generates tools without a rewrite, and keeps them current as the apps evolve.

03
Illustration of a multi-product SaaS platform use case for Pontil

Multi-product platform

You sell a portfolio. Each product has its own backend, its own API patterns, its own team. An API rewrite for one product is hard enough. Across the portfolio it's a non-starter. Agents need to reach all of it. Tools are generated and maintained across the portfolio in parallel. One platform, one approach, every product.

Don't see your platform? Let’s chat to see if Pontil is the right fit.

security

We don't cross the boundary. We become part of it.

Data never leaves your trust boundary. Pontil runs inside the infrastructure you already operate, authenticates as your users, and writes audit trails your security team can read the same way they read everything else.

Diagram of Pontil's security architecture and data boundary

Want to talk through the specifics for your environment?

how pontil compares

Where Pontil fits versus the alternatives.

Approach
Reaches backend capability
Self-maintaining
Runs as the user
Source code remains private
Works across portoflio
Pontil

API rewrite

X

iPaaS

X
X
X

Agent framework

X
X
X

Connector vendor

X
X

Frontier LLM provider integrations

X
X
X

Want to talk through the specifics for your environment?

Frequently asked questions

What languages and frameworks does Pontil support?
Does Pontil support the Model Context Protocol (MCP)?
How is Pontil different from an iPaaS like Workato or Prismatic?
How is Pontil different from an agent framework like LangChain or CrewAI?
How long does it take to get Pontil running?
Can Pontil work on internal apps, not just commercial SaaS?
Does Pontil work for multi-tenant SaaS platforms?
What language is the Agent SDK written in?
How much engineering time does Pontil need from our team?
What does Pontil cost?