Think inside your AI world.
Paste any webhook to be told when your AI needs you
Two products can look identical from the outside and be built the opposite way round. One supports Slack and Discord, and everything else waits its turn behind a roadmap. The other accepts an endpoint, and Slack and Discord happen to be endpoints. This is the second kind, and the difference shows up on the day you want the third destination.
Direct answer: paste the URL of anything that accepts a POST, and the moments that need a person land there. Your automation platform, your own small service, a channel in a chat tool, an internal endpoint that pages whoever is on call. The destination is recognised once, when you connect it, so no message costs a lookup afterwards. The URL is held as a credential, shown back only as its last four characters, revocable, and re-pasting rotates it in place.
A paste target, not a list of supported destinations
The connection is a URL you paste, so there is no list of supported destinations to be on or off. Anything that accepts a POST and answers is reachable, which includes the well‑known chat tools, the automation platforms people wire their own workflows in, and the small internal service that already knows how your team is paged.
This is why there is nothing to install. The endpoint you pasted is the integration, and removing it is deleting that endpoint. Nothing else was added to your workspace to be found and removed later.
How an unfamiliar destination is understood
Endpoints differ in small ways that matter: which JSON key carries the message text, how long a message may be, and how a link should be written so it renders as a link. Common destinations are already known, and answer for free. An unfamiliar one is worked out once, at the moment you connect it, and the answer is stored with the connection, so no message afterwards costs a lookup.
One detail in that is worth stating plainly, because it is a security property rather than an implementation note. A webhook URL’s path IS its secret: whoever holds the full URL can post to your channel. So when an unfamiliar destination has to be worked out, only the host is used. The path never leaves the vault, and a model never sees the URL.
Held as a credential, because that is what it is
The URL is encrypted at rest and shown back to you as its last four characters, the same way a key is. You can revoke it. Pasting a fresh URL rotates it in place rather than adding a second live endpoint, so there is never a forgotten destination still receiving your work’s interruptions after you thought you had moved them.
Delivery is recorded per attempt, so the question of whether a message actually landed is answerable without opening the destination and without decrypting the endpoint. A message that fired and did not arrive is the one failure nobody else can see, since the channel that would have told you is the channel that is broken.
What is sent, and what is refused
What is sent is short by design: the reason the work stopped, the agent that stopped it, one load‑bearing sentence, and a link that carries the item’s address rather than its contents. Opening the link pulls the item with its reasoning, live, so the message never has to be current, only the reading does. Where the destination caps message length, the text gives way and the link never does.
What is refused is the judgment. Which classes of moment land on an endpoint is your switch, and the classes raised about the system itself are off until you turn them on. Timeouts, escalation, what counts as blocking, and whether work holds or proceeds are not set here and not inferred. Sending is an emission, never a wait.
The connection is an endpoint you paste rather than a destination we support, so the third place you want to be told is the same amount of work as the first; the destination is understood once at connect from its host alone, the URL is held as a rotatable credential, and every message carries an address rather than a copy.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What counts as a valid endpoint?
Anything that accepts a POST with a JSON body and answers. That covers the chat tools most teams already watch, the automation platforms people build their own workflows in, and a service you wrote yourself. If it can receive a POST, it can receive this.
Is my webhook URL safe?
It is treated as a secret, because it is one: a webhook URL’s path is what authorises posting to your channel. It is encrypted at rest, shown back only as its last four characters, and revocable. When an unfamiliar destination has to be recognised, only the host is used, so the path is never disclosed in the process.
Does every message cost a lookup?
No. A destination is worked out once, when you connect it, and the answer is stored with the connection. Afterwards, sending is sending.
What happens if the destination is down?
Each attempt is recorded, so a message that fired and did not land is visible as its own fact rather than as silence. That matters more than it first sounds: when the channel that would tell you is the channel that is broken, silence and success look identical from where you are standing.
Can I point different kinds of event at different places?
Yes. Routing is per endpoint: each pasted URL carries which classes of moment may land on it. Questions can go where you will see them quickly and finished work somewhere quieter, or nowhere.
What this is
Think inside your AI world — you stay in command
Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.
It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.
Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:
Alpha is invite-only · free at launch.