canonical: https://jentic.com/apis/swaggerhub.lmorenoo/bienes-raices-api

# Lmorenoo Bienes Raices API

API para el manejo de bienes raices. The API exposes 7 endpoints.

## For AI agents

Programmatically crear un tipo de inmueble, buscar un topo de bien raiz. Covers 7 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- crear un tipo de inmueble
- buscar un topo de bien raiz
- actualizar un inmueble
- Query and filter Bienes Raices API records by parameters
- Monitor Bienes Raices API operational status and events

## Use cases

### Developer Tools Operations

Use the Bienes Raices API to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including crear un tipo de inmueble, buscar un topo de bien raiz, crear un inmueble.

Example prompt: Call POST `/tipoInmueble/{idTipoInmueble}` to crear un tipo de inmueble

### Automated administradores Management

Automate administradores operations by combining multiple Bienes Raices API endpoints. Agents can buscar un topo de bien raiz and then crear un inmueble in a single workflow.

Example prompt: Call GET `/tipoInmueble/{idTipoInmueble}` to buscar un topo de bien raiz, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bienes Raices API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'crear un tipo de inmueble', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tipoInmueble/{idTipoInmueble}` | crear un tipo de inmueble |
| GET | `/tipoInmueble/{idTipoInmueble}` | buscar un topo de bien raiz |
| POST | `/inmueble/{idInmueble}` | crear un inmueble |
| GET | `/inmueble/{idInmueble}` | buscar un inmueble |
| PUT | `/inmueble/{idInmueble}` | actualizar un inmueble |
| POST | `/negocio/{idNegocio}` | crear un negocio |
| GET | `/negocio/{idNegocio}` | buscar un negocio |

## Key resources

- **administradores** — Administradores de bienes raices
- **negociadores** — Operadores para compradores
- **invitadores** — Operadores para invitados

## Why Jentic

- **Setup:** Wiring the Bienes Raices API by hand means mapping its property-type, property, and deal routes, coding each GET, POST, and PUT, and handling retries yourself. Through Jentic you install once, import the Bienes Raices API from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This API puts the resource id in the URL path (`/inmueble/{idInmueble}`, `/negocio/{idNegocio}`), so a rule can pin your agent to one property or deal: it can read that resource and nothing else. You choose the operations it may call, so a property update or create path is not included unless you add it.
- **Credential handling:** Any access details for the Bienes Raices API are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a property type' or 'read a property', and Jentic returns the matching Bienes Raices API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Bienes Raices API use?

The Bienes Raices API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I crear un tipo de inmueble with the Bienes Raices API?

Yes. Use the POST `/tipoInmueble/{idTipoInmueble}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Bienes Raices API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I crear un tipo de inmueble through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'crear un tipo de inmueble'. Jentic returns the matching Bienes Raices API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bienes Raices API have?

The Bienes Raices API exposes 7 endpoints covering administradores, negociadores, invitadores operations.

### Can I limit what my agent is allowed to do with the Bienes Raices API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Bienes Raices API operations and credentials the agent may use. Since this API carries the resource id in the URL path, such as `/inmueble/{idInmueble}` and `/negocio/{idNegocio}`, you can pin the agent to a single property or deal and grant only the read call (GET) while withholding create and update paths like POST or PUT `/inmueble/{idInmueble}.` The agent can invoke nothing you have not explicitly allowed.