Bring your service to the people who organize their day and their money by chat. You bring what your service does; Jacko brings it into the right conversation.
It is the piece that lets Jacko use your service on someone's behalf, with their permission. They ask in their chat, Jacko calls your service and answers with what it found, without opening another app.
What's playing near me tonight?
Your service returns the showtimes
Tonight at 7:40 and 9:15 at your usual theater. Want a reminder at 7?
This is what you define. We take care of the chat, the channels and the context.
connector: cines-del-sur
name: Cines del Sur
category: entertainment
countries: [PE, CL]
auth: oauth2
actions:
search_showtimes: # read
input: { city, date, movie? }
book_seats: # write, needs a yes
input: { showtime_id, seats }
events:
- ticket.reminder
skill: |
When they ask what is playing, search
their city for today first. Offer a
reminder before the show.
context: [locale, country,
currency, timezone]Connectors build on MCP (Model Context Protocol), the open standard for assistants to use external tools. If your service already has an MCP server, you are a good part of the way there.
Your connector gets only what it needs. Anything beyond the basics is authorized by the person when connecting, one by one, and they can take it back any time.
context.localeLanguage. To answer in the person's language.
context.countryCountry. To show what applies where they live.
context.currencyCurrency. So amounts make sense.
context.timezoneTime zone. So times and reminders are theirs.
profile:nameName. Their first name, to greet them or book in their name.
profile:emailEmail. To send confirmations or link their account.
profile:phonePhone. Only if your service needs it for a booking or a delivery.
location:cityCity. To search what is nearby, without the exact address.
location:currentLocation at the moment. Only when the person shares it in the chat for that request.
calendar:freebusyCalendar availability. Free or busy at a time, never the details of their events.
payments:merchantPayments to your service. The transactions the person made with your business, nothing else.
conversationThe whole conversation. You only get the data of the action being run.
connectors.*Other connectors' data. What they share with one service, another one never sees.
bank.credentialsBank credentials and balances. No passwords, balances or their other accounts.
contactsTheir contacts. Not their address book or who they talk to.
permissions:
required: [location:city]
optional: [profile:name, calendar:freebusy]
actions:
search_showtimes:
kind: read
uses: [location:city]
book_seats:
kind: write # needs a yes
uses: [profile:name]POST /actions/search_showtimes
{
"request_id": "req_8f2c1a",
"context": {
"locale": "es-PE",
"country": "PE",
"currency": "PEN",
"timezone": "America/Lima"
},
"granted": {
"location:city": "Lima"
},
"input": { "date": "2026-11-03" }
}Each permission is shown to the person when connecting and they can revoke it from their account. If an action needs a permission it does not have, Jacko asks for it before calling it. Illustrative example.
Your service inside WhatsApp, Telegram and the web, without anyone installing another app.
A page with your brand, what your connector does and the verified badge once it passes review.
We review permissions, data and actions before publishing, so people trust connecting it.
We design the actions and events of your first connector with you, and test it together.
What your service does and what it would solve for people in the chat.
We define the actions, events and skill of your connector.
With our help, or we build it with you.
It passes the security review and shows up in the catalog.
It is the piece that lets Jacko use your service on someone's behalf, with their permission, inside WhatsApp, Telegram and the web. They ask in the chat and Jacko answers with what your service returns.
It is not required. If you already have an MCP server you move faster; if your service has an API, we design the connector with you.
Always the language, country, currency and time zone. Anything else, like their name or city, only if the person authorizes it. Never the whole conversation.
No. Any action that creates, changes or pays for something is confirmed with the person first.
You choose: every country where Jacko works, or only some of them.
Write to us with the form on this page. Public docs are coming soon, and people who write now see them first.
Leave your details and we will write to get started. Public docs are coming soon; people who write now see them first.