Install Jentic One Beta

Connect the Bienes Raices API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bienes Raices API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.lmorenoo%2Fbienes-raices-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.lmorenoo%2Fbienes-raices-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Bienes Raices API.

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

GET STARTED

Start building with Bienes Raices API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

7 endpoints — api para el manejo de bienes raices.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Bienes Raices API through Jentic.

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.

Lmorenoo Bienes Raices API

Name: Bienes Raices API
Brand: Bienes Raices API
Availability: InStock

Browse all Swaggerhub Lmorenoo APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to crear un tipo de inmueble, I want to buscar un topo de bien raiz, Search for crear un inmueble, Find all buscar un inmueble

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

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

Jentic One on Github View OpenAPI Document

Connect the Bienes Raices API to your agent

Capabilities

Start building with Bienes Raices API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lmorenoo Bienes Raices API