Reference & Lookup Data · Integration
Cutt.ly
Add Cutt.ly to your product for your customers, and give your AI agents governed access to it.
Cutt.ly exposes a single query-string endpoint, api.php, where the operation is chosen by which parameters you send alongside the key: shorten, stats, edit or delete. Responses nest under a url object and report the outcome as a numeric status field inside the body, so an application-level failure such as an already-taken back-half has to be read from that field rather than from the HTTP status. Custom back-halves are requested with a name parameter and compete across the whole shared cutt.ly namespace unless the account has its own branded domain, so collisions are frequent on common words. Statistics come back as cumulative counters plus breakdowns by referrer, country and device, not as an event stream, so there is no per-click record to page through or to join on a timestamp. Of the available catalogue categories this is the least-wrong fit: Cutt.ly holds links and their click reports rather than campaigns or subscribers. fastn holds each customer's key and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cutt.ly account so short links are created under their branded domain.
Generate a short link whenever your product publishes a shareable asset, retrying on a taken back-half.
Pull cumulative click counts onto a campaign record so performance sits beside the content.
Show referrer and country breakdowns for a link inside your own reporting screen.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent how many clicks a named short link has had and where from, with each call audited per tenant.
Have an agent check whether a proposed back-half is available before a link is published.
Let an agent shorten an approved URL and return the link for inclusion in a draft message.
Example prompt
How many clicks has our launch short link had, and from which countries?
Set up Cutt.ly in 4 steps
- 01Enable the Cutt.ly connector from your fastn dashboard.
- 02Have each customer authorise their own Cutt.ly account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Cutt.ly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cutt.ly integration without building it. Your customers connect their own Cutt.ly account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cutt.ly update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cutt.ly connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Cutt.ly, across other categories.
Salesforce
HubSpot
Notion
SnowflakeCutt.ly integration FAQ
How do I add a Cutt.ly integration to my product?
Enable the Cutt.ly connector in your fastn dashboard, then let each customer authenticate their own Cutt.ly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cutt.ly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cutt.ly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cutt.ly account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Cutt.ly integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent how many clicks a named short link has had and where from, with each call audited per tenant.
Who maintains the Cutt.ly integration?
fastn does. When Cutt.ly changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Cutt.ly lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Cutt.ly results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Cutt.ly is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Cutt.ly integration?
A common starting point: let a customer connect their own Cutt.ly account so short links are created under their branded domain. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Cutt.ly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cutt.ly does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cutt.ly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.