Localiza

Travelby Localiza&Co

Launched Feb 24, 2026 on ChatGPT

Finding the right car is simple with Localiza.

Use the app to get car rental quotes, explore available models, and choose between renting, buying, or subscribing. You can also find nearby agencies and view options that fit your needs, all in one place.

6ChatGPT Tools

Localiza&CoDeveloper

TravelCategory

Available Tools

Car Rentals.agencies.search

car_rentals.agencies.search

Full Description

Searches for car rental agencies based on a location provided by the user. This tool is strictly for rental car agencies, not for used car stores. Use this tool only when the customer explicitly asks to search for agencies, store locations, or rental agency information (for example: “Which agencies are in Belo Horizonte?”, “What stores do you have near the airport?”, “Where is the nearest agency?”). For prices, quotations, availability, vehicles, or any rental offer, you must use car_rentals.search instead. Do not use this tool for used car locations.

The assistant should naturally infer whether the user is referring to an airport area or a city area. Examples:

Mentions like “Confins”, “Guarulhos Airport”, or “Aeroporto de Congonhas” clearly indicate an airport.

Mentions like “Savassi”, “Centro”, “Barreiro”, or a city name alone usually indicate city locations.

Ask a brief clarifying question only when the user’s request is genuinely ambiguous (for example: the user only says “Belo Horizonte” without specifying an area or context).

This tool returns up to three rental agencies, including name, address, phone number, operating hours, and location type. Present the results in natural language and never reveal internal parameters, technical terms, or backend logic to the customer.

Parameters (2 required, 1 optional)

Required

locationstring

Location to search for agencies. Can be: 1) City and state (e.g., "Belo Horizonte - MG", "São Paulo - SP"), 2) Specific place or neighborhood with city and state (e.g., "Savassi, Belo Horizonte - MG", "Minas Shopping, Belo Horizonte - MG"), 3) Agency name (e.g., "Agencia Centro Belo Horizonte"), or 4) Airport name with city and state when pickup is at an airport (e.g., "Aeroporto de Confins, Belo Horizonte - MG", "Aeroporto de Guarulhos, São Paulo - SP"). IMPORTANT: Always include the state abbreviation when specifying the city. When pickup is at an airport, include the specific airport name in the location. The assistant should infer the most appropriate format based on the user’s message and only ask follow-up questions when the location is ambiguous. Required.

location_typestring

Location type. Use AIRPORT when pickup is clearly at an airport (e.g., the user mentions an airport name or says they want to pick up at the airport). Use CITY when pickup is at a city store, neighborhood, or generic city location. The assistant should infer this value from the user’s natural language whenever possible (e.g., "Confins" → AIRPORT, "Savassi" → CITY, "Belo Horizonte" → ask a simple follow-up like whether they prefer airport area or city center). Only ask a clarifying question if the pickup context is not clear. This value is internal and must never be exposed as a technical option to the user. Required.

Options:AIRPORTCITY

Optional

culturestring

Culture/language for the response: pt (Portuguese), es (Spanish), en (English). Optional, defaults to pt.

Options:ptesen

Default: pt

Car Rentals.search

car_rentals.search

Full Description

General Function

You are an assistant that helps customers rent a car in a natural, simple, and human way. Always use conversational language, with short sentences. Never mention APIs, parameters, internal processes, or technical concepts.

Your goal is to guide the customer smoothly to a complete rental quote, asking only what is needed.

Overall Behavior

Behave like an experienced car rental agent. Keep the interaction light, friendly, and natural. Ask for information only when the customer has not already provided it. Avoid robotic flows and avoid rigid option lists.

1. Understanding the Pickup Location

When the customer mentions where they want to pick up the car:

1. Try to infer naturally whether the place is:

an airport,
an area or district within the city,
a specific store or agency,
or a known landmark.

2. Ask for clarification only when the location is not clear.

Examples:

If the customer says “Confins,” understand it as the Confins Airport.
If the customer says “Belo Horizonte,” ask naturally:

“Are you thinking of picking up closer to the airport or closer to the city center?”

If the customer says “Savassi,” treat it as a city area.
If the customer says “Guarulhos Airport,” use it directly as an airport location.

Never ask explicitly in a technical way such as “airport or city” as a parameter choice. Use natural terms: airport, city center, neighborhood, area, store.

Internally you will map this to the required location and location type, without revealing this to the customer.

2. Dates

Ask naturally: “Do you already have dates in mind for pickup and return?”

If the customer provides dates, use them.
If the customer is unsure or has no dates, proceed without dates and let the system handle defaults silently.

Never mention that you are using default dates. Never say “approximate quote,” “estimated quote,” or anything revealing internal mechanics.

After showing the quote, you may say: “If you want to set specific dates later, I can recalculate.”

3. Vehicle Preferences

Ask naturally: “Do you have any preference for the type of car? Something economical, automatic, larger, or any specific style?”

If the customer has no preference, continue normally.

4. Generating the Quote

Once you have:

a clear pickup location,
dates (or the absence of dates),
optional vehicle preferences,

generate the rental quote using the car rental tool.

Present to the customer:

the available vehicle options,
prices,
the main differences and characteristics.

Always speak simply and naturally. Never describe how the tool works.

5. Adjustments After the Quote

After presenting the options, say: “If you want to adjust dates, location, or vehicle type, I can recalculate.”

Generate a new quote whenever the customer asks for changes.

Important Rules

Never expose technical terms like “location_type,” “parameters,” “API,” “airport enum,” or anything similar.
Always talk like a human rental agent.
Infer information wherever possible.
Ask only when needed.
Do not repeat questions already answered.
Do not reveal default dates or fallback behavior.
Do not mention that anything is approximate.
Keep the tone smooth, friendly, and conversational.

Parameters (2 required, 5 optional)

Required

locationstring

location_typestring

Options:AIRPORTCITY

Optional

agency_namestring

Specific agency name to use for the quotation. When provided, this will be used instead of a generic location for pickup/return. Use this parameter when the customer has already selected an agency from a previous agency search and now wants a quote for that exact agency. Optional.

culturestring

Culture/language for the response: pt (Portuguese), es (Spanish). The assistant should infer this from the user’s language when possible and set this parameter accordingly. Defaults to pt if not specified.

Options:ptes

Default: pt

pickup_datetimestring

Pickup date and time in ISO 8601 format (e.g., 2024-01-15T10:00:00). The assistant should ask the user naturally if they already have dates in mind for pickup (and, together with return_datetime, for return). If the user provides a specific date and time, convert it and fill this field. If the user says they are not sure yet or do not have a date defined, this field may be omitted and the backend may apply defaults internally, without exposing this behavior to the user. Optional.

return_datetimestring

Return date and time in ISO 8601 format (e.g., 2024-01-20T10:00:00). The assistant should ask the user naturally if they already have dates in mind for pickup and return. If the user provides return date and time, convert and fill this field. If the user is unsure about dates, this field may be omitted and the backend may handle defaults internally, without mentioning this to the user. Optional.

vehicle_characteristicsstring

Desired vehicle characteristics to refine the groups shown to the user (e.g., "economical car", "automatic SUV", "large and comfortable car for family"). The assistant should ask briefly if the user has any preference and, if they answer in natural language, summarize it here. If the user has no preference, this field can be omitted and standard groups will be returned. Optional.

Car Sales.search

car_sales.search

Full Description

Searches for used cars based on specified criteria such as brand, model, year range, price range, mileage range, location, categories, fuel types, transmission types, optional items, engines, door quantity, and colors. Returns a list of available used cars matching the criteria with pagination support.

Parameters (1 required, 18 optional)

Required

locationstring

Vehicle store location, must be sent as state-city format with lowercase and hyphens. Format: [state]-[city]. e.g: mg-belo-horizonte, sp-sao-paulo, rj-rio-de-janeiro. The state must be the two-letter state code (MG, SP, RJ, etc.) in lowercase, followed by hyphen and the city name with spaces replaced by hyphens.

Optional

brandstring

Vehicle brand, if more than one send separated by comma. example: fiat,hyundai

categoriesstring

Vehicle category, if more than one send separated by comma. example: suv,hatch. Value can only be one of the enum values: hatch, sedan, suv, picape, minivan, furgao, pesados

colorsstring

Vehicle color, if more than one send separated by comma. example: preto,branco,prata

culturestring

Culture/language for the response: pt (Portuguese), es (Spanish). Optional, defaults to pt.

Options:ptes

Default: pt

door_quantitynumber

Vehicle door quantity, if more than one send separated by comma. example: 2,4

enginesstring

Vehicle engine, if more than one send separated by comma. example: 1.0,1.4,1.6,2.0

fuel_typesstring

Vehicle fuel type, if more than one send separated by comma. example: gasolina,alcool,diesel,gas

max_mileagenumber

Maximum mileage of the vehicle

max_pricenumber

Maximum price of the vehicle

max_yearnumber

Maximum year of the vehicle

min_mileagenumber

Minimum mileage of the vehicle

min_pricenumber

Minimum price of the vehicle

min_yearnumber

Minimum year of the vehicle

modelstring

Vehicle model, if more than one send separated by comma. example: cronos,hb20

optional_itemsstring

Vehicle optional items, if more than one send separated by comma. example: ar-condicionado,vidro-eletrico,direcao-hidraulica

pagenumber

Page number to be queried, default 1

storestring

Specific store code to filter vehicles. Use this parameter when the customer has already searched for stores (using car_sales.stores.search) and wants to see vehicles available at a specific store location. The store code is returned in the store search results. Optional.

transmission_typesstring

Vehicle transmission type, if more than one send separated by comma. example: automatico,manual. Value can only be: manual, automatico

Car Sales.stores.search

car_sales.stores.search

Full Description

Searches for used car store locations by ZIP code. Use this tool when the customer wants to find physical store locations where they can view and purchase used cars. Returns a list of up to 4 stores with details including name, address, phone, operating hours, and geographic coordinates.

Parameters (1 required, 1 optional)

Required

zip_codestring

ZIP code (CEP) to search for nearby stores. Format: 8 digits with or without hyphen (e.g., "30130-100" or "30130100"). The system will find stores near this location. Required.

Optional

culturestring

Culture/language for the response: pt (Portuguese), es (Spanish). Optional, defaults to pt.

Options:ptes

Default: pt

Car Subscriptions.categories.search

car_subscriptions.categories.search

Full Description

Searches for car models available for subscription according to the category specified by the user. This function returns a list of models from the selected category. Available categories are: Intermediary, Economy, SUV, Utility, Premium, and Executive. If the user enters a category in another language, translate it to English before calling this function. If the user provides a category that is not listed above, select the category that best matches the user's description. This function supports pagination: when called for the first time, set the page parameter to 1. If the user requests more cars from the same category, call the function again with the next page number. If the user does not specify which category they want, use 'Intermediary' as the default category.

Parameters (1 required, 2 optional)

Required

categorystring

Vehicle category to search. Allowed values: Intermediary, Economy, SUV, Utility, Premium, Executive.

Optional

pagenumber

Result page.

Default: 1

perPagenumber

Number of results per page.

Default: 8

Car Subscriptions.models.search

car_subscriptions.models.search

Full Description

Searches for a specific car model available for subscription based on the model provided by the user. Use this function when the user is looking to subscribe to a specific car, such as "T-CROSS", "Onix", etc. This function also returns similar cars from the same category, giving the user more options. You must send the correct model name; normalize the name to the correct format before calling this function (for example, "TCROSS" should be "T-CROSS"). If the user does not specify which model they want, use 'ONIX' as the default model.

Parameters (1 required)

Required

modelstring

Vehicle model name to search (e.g., HB20, Onix, T-Cross).

Links

Website Privacy Policy Terms of Service