Imports assets from a URL into a named gallery, polls upload status, aborts an import in progress, and returns an embeddable upload widget URL.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro uploads a media asset directly from an external URL. Your content library grows without manual file downloads.
Ayro checks the upload progress of a media asset by status ID. You know when your asset is ready to use.
Ayro cancels an ongoing asset upload. You can stop and retry without clutter in your library.
Each card is one request a support team gets, and the Cincopa actions Ayro runs to close it.
Ayro uploads an asset directly from an external URL, targets a specific gallery or an existing asset, and returns the status ID that tracks the import from then on.
Ayro polls the upload by its status ID and reports whether the file has finished, so nobody refreshes the media library waiting on a large video to land.
When the wrong link was sent or a transfer is dragging on, Ayro aborts the upload in progress by its status ID rather than letting it complete and cleaning up afterwards.
Ayro generates the Cincopa upload iframe URL for a gallery, so a person who needs to send a file gets an embeddable upload widget in the conversation and the asset lands in the right place.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Cincopa actions it has and picks the ones a request needs.
Authorize the Cincopa account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Cincopa actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeCincopa · Ayro
What can you do in Cincopa without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Cincopa.
Not as a direct file transfer. Upload Asset From URL takes a publicly reachable external URL rather than a binary, so the file needs a link Cincopa can fetch. For the other direction, Get Upload Iframe returns a widget URL the person can upload through themselves.
All 5 actions your agent can call on Cincopa, straight from the live MCP connection.
Upload a new asset directly from a provided external URL and receive a status ID for tracking.
Abort an ongoing asset upload-in-progress by providing its status ID.
Check the status of an asset upload initiated via URL by its status ID.
Get an upload iframe URL for embedding an upload widget.
Validate API connection.
Same connection, same setup. Pick the next one your team already uses.
Searches ChatFAI's public characters by name or keyword, returns one by ID, and lists the connected account's conversations.
Speaks a written reply in a chosen voice, enforces pronunciation rules for product names, dubs recordings into other languages, and reports on outbound call batches.
Looks up Headout booking data and triggers updates from inside the conversation.
Retrieves live breaking headlines, searches the article archive by keyword or domain, and confirms which publisher IDs are valid to filter on.
Resolves SoundCloud links, uploads and corrects tracks, curates playlists, and reports the comments and reposts a release is collecting.
Searches events by location and date, returns venue and seating detail, and resolves artists and teams to their attraction records.

Authorize the account and your agent has all 5 actions from the first conversation.
