Platform
fastn Connect
Previously the Unified Context Layer, or UCL. Same product, new name.
One governed layer between your agents and the systems your customers already run. Each connection is authorised by the customer who owns it, scoped to their permissions, and audited on every call, so an agent reaches exactly what that customer allowed and nothing belonging to anyone else.
If you searched for UCL or Adaptive Context
You are in the right place. The Unified Context Layer was renamed fastn Connect, and Adaptive Context was an earlier name for the same thing. Our blog still refers to UCL throughout, because those posts were written under the old name and describe this product.
What it does
Every call runs under one customer's own credentials with the permissions that customer granted. Tokens and refresh are managed for you, so a mistake reaches one tenant's data rather than all of them.
Point an MCP client at fastn and the agent discovers each connected system as a callable action, covering CRM, ticketing, finance and HR through a single connection, with no per-tool code to write.
Each action an agent takes is logged and attributable. That record is usually what makes the difference between an enterprise piloting an agent and letting it act inside their tenant.
Call one CRM API instead of learning Salesforce, HubSpot and Pipedrive separately. Unlike rigid unified APIs, each customer's own custom fields, objects and pipelines pass through rather than being flattened away.
Chain steps across a customer's connected systems, started by a webhook, a schedule, an API call or a detected change, with retries and per-step logging. Ship one workflow, and it runs isolated under each customer's own auth.
Describe the system a customer needs and an integration agent generates the connector and tests it against the live API. When a vendor changes that API, the agent adapts the connector.
What it is made of
One endpoint your agents point at, with per-tenant auth, scoped permissions and an audit trail on every call.
One normalised schema per category, with each customer's own custom fields passed through rather than flattened away.
Multi-step automations across a customer's connected systems, triggered by events, schedules or API calls.
Agents that build, test and maintain the connections rather than leaving that work in your backlog.
Questions
Is fastn Connect the same as the Unified Context Layer?
Yes. UCL was renamed to fastn Connect for branding. It is the same product and the same architecture, so anything written about the Unified Context Layer, including the posts in our blog, describes fastn Connect.
What happened to Adaptive Context?
Also fastn Connect. Adaptive Context was an earlier name for the same layer. If you arrived looking for either name, this is the page you wanted.
What does the layer actually do?
It sits between your agents or your product and the systems your customers already run, so a request reaches exactly one customer's data with their own credentials, their own permissions, and a record of what was read or written.
Do my customers connect their own accounts?
Yes. Every connection is scoped to an individual customer, so each authorises their own account and reaches only their own data. That per-tenant isolation is the point: you support the long tail of customer setups without maintaining an integration per customer.
Connect one system and see what your customer would see.
Start free