Integration · Run stores and orders
Chilexpress and Meteor AI agents
Connect the Chilexpress API to a Meteor AI agent: coverage by district with no credentials, shipment quoting and parcel tracking. 8 real tools.
How does Chilexpress connect to Meteor?
Meteor connects to the Chilean carrier Chilexpress so your Met can confirm whether it reaches a district, resolve that district's code even when the customer types it with accents, quote a shipment with its service options and track a transport order. There are 8 tools and none of them writes: creating the order produces a real label and a real charge, so it was left out on purpose. Coverage works with no credentials at all, in test and in production, so a Met can answer "do you deliver to Puerto Varas?" on day one. Quoting and tracking each require their own key from the Chilexpress portal.
Where it applies: Chile. The Chilexpress district code is four letters and it is not the country's official code: the connector resolves it from the name and forces you to disambiguate identical names.
What it automates
What a Meteor Met does with Chilexpress
Answer do you deliver to my district before signing up
Chilexpress coverage is an open interface: it answers with no credentials, in test and in production. Your Met resolves the district code from whatever name the customer typed and confirms coverage, even before there is a signed contract in place.
Give the shipping cost inside the conversation
With origin, destination and parcel dimensions, your Met requests the quote and returns the service options with their price and the final chargeable weight. Volumetric weight is resolved by Chilexpress, never by a calculation on the Meteor side.
Disambiguate the district instead of guessing it
The Chilexpress master list ships without accents, and some districts share a name across regions. When more than one match shows up, the connector returns them all and forces the question. It never picks one on its own.
Follow an order with the wording the carrier gives
Your Met tracks by transport order number or by the internal reference of the order, and returns the events with date and time. Since Chilexpress publishes no stable status codes, the answer leans on the description of the last event and does not reinterpret it.
8 tools
Everything your Met can ask Chilexpress 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 |
|---|---|
chilexpress_consultar_conexion | Reports what is configured in this workspace: environment, which keys are loaded and the default origin. |
chilexpress_listar_regiones | Lists the sixteen regions of Chile with their Chilexpress code. It needs no credentials. |
chilexpress_buscar_comuna | Finds a district by name and returns its four letter code, matching it with or without accents. |
chilexpress_consultar_cobertura | Says whether Chilexpress reaches a district and under what mode. It answers with no credentials. |
chilexpress_listar_comunas | Lists the districts and localities covered in a region, to show options to someone unsure of the exact name. |
chilexpress_cotizar_envio | Returns the service options with their price, the final chargeable weight and their conditions. |
chilexpress_rastrear_envio | Tracks a transport order by its number or by the reference it was created with, with its events. |
chilexpress_validar_direccion | Splits a Chilean address into street, number and unit, which is how Chilexpress asks for them. |
The limits
What the Chilexpress integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not create transport orders or labels. This integration is read only: creating a shipment produces a real label and a real charge, it is irreversible, and it belongs to a later phase.
-
It does not return your negotiated rate. Chilexpress states on its own portal that its quoting service does not take discounts or special rates into account, so the figure is the list price. That is the opposite of TCC and Andreani, where price comes from your contract.
-
It does not validate addresses against an official catalog. Chilexpress does not expose that check, so the connector only splits street, number and unit, and flags a missing number.
-
It does not normalize shipment status. Chilexpress returns events as free text with no stable codes, so there is no comparable status across shipments or across carriers.
-
It does not open production on its own. Test keys come straight from the portal, but production keys require ten simulated orders, their labels emailed to support and a human review, and the account starts with a monthly shipment cap.
-
It does not use one credential for everything. Quoting and tracking are two separate products in the portal with two separate keys, and loading one into the other is rejected.
Before you start
What you need to connect Chilexpress
- 1
Nothing, if all you need is coverage
The Chilexpress coverage interface is open and answers with no credentials, in test and in production. It is the first thing a Met can answer, with no paperwork beforehand.
- 2
A key for the quoting product
From the Chilexpress developer portal, by subscribing to the quoting product. The test key comes on its own; the production one goes through the manual certification process.
- 3
A key for the shipping product and the company tax ID
The key belongs to the transport orders product, used here only for tracking, and it is a different key from the quoting one. The tax ID can be pasted with dots and check digit.
- 4
Origin district and environment (optional)
The district you ship from is configured once with its four letter code, so you do not repeat it on every quote. The environment starts in test.
Frequently asked questions
Questions about Chilexpress and Meteor
Not necessarily. Chilexpress states on its portal that its quote does not take discounts or special rates into account, so what arrives is the list price. If you have a commercial agreement, your real price is lower and the conversation should say so.
Not yet. This integration checks coverage, quotes and tracks, but it does not write to Chilexpress. Creating the transport order produces a real label and a real charge, it is irreversible and it could not be exercised against the API, so it was left for a later phase.
Not for coverage. That interface answers with no credentials, in test and in production, so a Met can confirm whether they deliver to a district from day one. Quoting and tracking do require a key, and each one needs its own.
By searching the name in the Chilexpress master list, which ships without accents. The connector compares ignoring those differences, so it finds the district even when the customer spells it correctly. If several match, it returns them all and forces a choice.
Because Chilexpress returns events as text and publishes no stable status codes. There is no normalized status to compare, so the answer leans on the description of the last event exactly as the carrier wrote it.
Step by step
Automations that use Chilexpress
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 Chilexpress?
We will show you with your own account connected, not with a canned demo.