Integration · Run stores and orders
Skydropx PRO and Meteor AI agents
Connect the Skydropx PRO API to a Meteor AI agent: quote 20 carriers across Colombia, Mexico and Chile, ship, collect and track. 15 tools.
How does Skydropx PRO connect to Meteor?
Meteor connects to Skydropx PRO, which is a parcel aggregator and not a carrier: with a single account your Met quotes across twenty carriers in Colombia, Mexico and Chile. You give it the route and it gets back, in one call, every carrier that serves it, sorted from cheapest to most expensive; once a person picks a rate it creates the label, returns the tracking number and the label address, checks whether the carrier will collect at that address and books the visit, finds nearby pickup points and explains the extra charges that show up on the invoice. There are 15 tools, named by operation and not by carrier: which one serves that route and at what price is exactly what you are asking the aggregator. It covers four of the five logistics stages and it is the only connector in the catalog that schedules a pickup. It never picks the rate for you and never answers "the cheapest one".
Where it applies: Colombia, Mexico, Chile. Country is data here, not a separate connector: the same API serves all three. What does change per account is the production host and which carriers that customer has enabled, so the real list for a route comes from the quote and not from the reference catalog.
What it automates
What a Meteor Met does with Skydropx PRO
One question, twenty answers
Your Met requests the quote for the route and gets back, in one call, every carrier that serves it, with service, total, currency and delivery days, sorted from cheapest to most expensive. In Colombia those are Interrapidisimo, Servientrega, Coordinadora, Envia, TCC and Deprisa; in Mexico, Estafeta, Redpack, Paquetexpress, 99 Minutos, J&T, Sendex and AMPM; in Chile, Starken, Blue Express, Chilexpress, Correos de Chile and J&T. And across all three countries, the international couriers: DHL, FedEx and UPS.
Quote with the carrier the customer asked for
When someone writes "quote it with Interrapidisimo", the carrier goes in as a parameter of the quote and of the coverage check. There is no tool per carrier, and that is deliberate: picking the tool would mean picking the carrier before having the price, which is the very thing being asked for.
Create the label only after an explicit yes
Creating the label spends the real balance of your account, so the tool requires the id of the rate that was already quoted plus a separate confirmation. The right order is to show carrier, service and total, wait for the person to answer and only then ship. The connector never completes that step on its own.
Track with the number the customer received
Your Met tracks by tracking number and carrier, because the same number can exist at two of them. The answer says which source the status came from, so whoever reads it knows whether they have the full movement history or only the current status of the shipment.
Check the balance before shipping and schedule the pickup
With no balance, creating the label fails with an error that does not always name the money, so your Met can check the credits before shipping. And once there are parcels ready, it first asks whether the carrier collects at that address and only then books the visit, on the agreed date, inside whatever time window you give it, across several shipments at once. It is the only connector in the catalog that goes that far: the others quote, ship or track, but the courier visit is arranged elsewhere. That covers four of the five logistics stages; the fifth, delivery, belongs to the carrier.
When the customer would rather collect it
Somebody does not want to wait at home. Your Met finds the pickup points and offices near their postal code, with address, city, opening hours and which carrier each one belongs to, and hands over the ones that suit them. The same list serves the merchant who prefers dropping parcels at a counter instead of waiting for the courier.
Explain the deduction the merchant does not recognise
A charge nobody asked for shows up and the dashboard does not explain it. Your Met lists the extra charges Skydropx billed to the account, such as reroutes, weight or size differences, returns and extended zones, with the concept, the amount and which shipment it belongs to. It reports them exactly as they come: no adding up, no recalculating, because what you dispute is the invoice.
15 tools
Everything your Met can ask Skydropx PRO for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
skydropx_consultar_conexion | Checks against the server that the credentials work and reports environment, host and configured country. |
skydropx_cotizar_envio | Quotes the route with every carrier that serves it, with several parcels and a declared value, and returns the list sorted from cheapest to most expensive. Ask for it and you also get the rates the carrier rejected, with the reason. |
skydropx_consultar_cobertura | Says whether there is delivery to a destination and with which carriers, by quoting a minimal parcel and hiding prices. |
skydropx_listar_transportadoras | Lists carriers: the real ones for a route if you give origin and destination, or the country reference catalog if you do not. |
skydropx_crear_envio | Creates the label from a rate that was already quoted and returns the tracking number and the label address. |
skydropx_cancelar_envio | Requests cancellation of a label that already exists, which the carrier then approves or rejects. |
skydropx_consultar_envio | Record of one shipment by its internal id: status, carrier, tracking number and label. |
skydropx_rastrear_envio | Tracks by tracking number and carrier, and says which source the status it returns came from. |
skydropx_listar_envios | Lists the account shipments in pages of up to twenty, to find one you only remember the date of. |
skydropx_obtener_etiqueta | Returns the address of the printable label of a shipment, never the file itself or its encoded contents. |
skydropx_buscar_puntos_de_retiro | Finds carrier pickup points and offices, with their address, city, opening hours and which carrier each one belongs to. |
skydropx_consultar_cobertura_recoleccion | Says whether the carrier will come and collect at an address, which is not the same question as whether they deliver to a destination. When the answer cannot tell, it returns unknown. |
skydropx_consultar_cargos_extra | Lists the extra charges Skydropx billed to the account: reroutes, weight or size differences, returns and extended zones, with concept and amount. |
skydropx_agendar_recoleccion | Books the carrier to come and collect several shipments on a date and, if you want, inside a time window. The answer says whether it was accepted. It requires a person to confirm. |
skydropx_consultar_saldo | Checks the balance and credits of the account, which is what gets spent every time a label is created. |
The limits
What the Skydropx PRO integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not pick the rate. It returns the full list sorted by price and the decision stays with whoever has the context: it never answers "the cheapest one" or drops options by itself.
-
It does not link your own carrier contract. That step is human and happens once in the Skydropx panel, under "Connections, Carriers": there is no endpoint to create it from Meteor, so there is none from your Met either.
-
It does not claim a rate is yours when it cannot tell. If the response carries nothing to distinguish it, the flag stays at "unknown" and not at "no": inventing a "no" would deny your contract without the data to deny it.
-
It does not notify you on its own when a shipment changes status. Skydropx does have webhooks, but the signature it sends them with is undocumented and they were left undeclared on purpose: an invented verifier is worse than no webhooks at all.
-
It does not bring responses confirmed against a real account. The Skydropx sandbox requires a signup that has to be done by hand, so the routes are verified by probing and the exact shape of each response is not.
-
It does not cancel a shipment by itself. It requests the cancellation and the carrier approves or rejects it, and it can be refused once the parcel has been collected.
-
It does not replace the direct connectors to a single carrier. Chilexpress and TCC have their own, with whatever their API exposes beyond this; here they show up as one more option.
-
It does not cover the fifth stage. It quotes, ships, checks the pickup, books the visit and tracks, but delivery belongs to the carrier and any incident on the road is settled with them, not from here.
-
It does not add up or recalculate the extra charges. It reports them exactly as Skydropx billed them, with concept and amount: a total recalculated by the connector would not match the invoice, and the invoice is what you dispute.
Before you start
What you need to connect Skydropx PRO
- 1
A Skydropx PRO Client ID and Client Secret
You copy them from your Skydropx PRO panel, under "Connections, API". It is self service: no support request and no waiting for someone to enable the account.
- 2
A test or production environment
It starts in test, which is free and spends no balance. Production is requested explicitly, and credentials from one environment do not work in the other.
- 3
The country of the account
Colombia, Mexico or Chile. It is the default country of the addresses and the one that filters the reference carrier catalog. It is configured once.
- 4
A production host, if your account is not on the main domain
Some Colombian accounts live on a Skydropx host of their own. The API contract is identical, so writing that host into the connector configuration is enough.
- 5
Origin postal code and the own contract flag (both optional)
The postal code you ship from saves repeating it on every quote. The own contract flag makes the response warn you when no negotiated rate shows up.
Frequently asked questions
Questions about Skydropx PRO and Meteor
Because quoting is a single call that returns every carrier on the route: seven tools would make the same request seven times and throw away the rest of the answer. And above all they would force you to pick the carrier before having the price, which is exactly what you are asking the aggregator. The carrier goes in as a parameter, on the quote and on the coverage check.
Yes, if you linked your contract beforehand in the Skydropx panel, under "Connections, Carriers". That link is a human step done once and it has no endpoint. From then on your negotiated prices arrive in the same list as the aggregator ones, and if you declared that you have a contract and no rate comes back flagged, the response warns you instead of quoting high in silence.
No, and that is a hard rule of the connector. It returns the full list sorted from cheapest to most expensive, with carrier, service, total and delivery days, and the decision belongs to whoever knows the case: sometimes what matters is the delivery date, not the price.
Yes. The connector starts in the Skydropx test environment, which is free and spends no balance. Creating a label in production does spend the real balance of your account, which is why that tool requires an explicit confirmation on top of the rate you already picked.
The API contract is a single one and the country travels as data, so the connector does not change between markets. What is not verified is whether an account from one country can quote routes in another: that is why country and host are configured separately and you can keep one configuration per market.
No, and mixing them up costs a wasted visit. Coverage says whether the carrier delivers to a destination; pickup coverage says whether they will collect at an origin. You check it before booking, because booking where they do not go is a failure the merchant finds out about late, when the courier never showed. And if the answer cannot tell, it comes back as unknown and never as a no: denying the pickup without the data is worse than not answering.
Chilexpress has a direct connector against its own API, and that page answers for what Chilexpress exposes beyond this, such as coverage by district with no credentials. This page answers for the aggregator: one account, twenty carriers and a quote that compares them. Chilexpress also shows up here, as one more option on the list.
Step by step
Automations that use Skydropx PRO
Complete tasks, with the steps and the tools that run at each one.
Run stores and orders
Other integrations in the same family
Want to see a Met running Skydropx PRO?
We will show you with your own account connected, not with a canned demo.