Install Jentic One Beta

Connect the Palomma Rentals API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Palomma Rentals 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%2Fpalomma.com%2Fpalomma" | 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%2Fpalomma.com%2Fpalomma" | 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 Palomma Rentals API.

Issue a rent invoice with reference, amount, description, redirectUrl, and customerDocumentNumber, and get back a paymentUrl for the tenant

Look up invoices by reference, contract, or customerDocumentNumber to see status, paymentDate, paymentMethod, and paymentAmount

List invoices paid or settled on a date with the paymentDate, settlementDate, and settlementCycle filters, paging with limit and cursor

Read a settlement by date and cycle to reconcile numberOfInvoices, amountCollected, fees, feesPostpaid, adjustments, and paymentAmount

GET STARTED

Start building with Palomma Rentals API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Palomma Rentals API for, with concrete tasks.

★ Agent-issued rent invoices through Jentic

A property manager's agent bills tenants at the start of the month. Through Jentic it finds the createInvoice operation, sends the reference, amount, description, redirectUrl, and the tenant's customerDocumentNumber with the lease contract, and returns the paymentUrl to send to the tenant. Your own Jentic One instance injects the Palomma API key, so the agent never sees it.

POST /invoices with reference 'APT-302-2026-11', amount 1800000, description 'November rent apartment 302', redirectUrl 'https://example.com/thanks', customerDocumentNumber '1020304050', documentType 'cc', and contract '2045', then return the paymentUrl

Payment status follow-up

Before sending a reminder, an agent checks which tenants have paid. Filtering GET /invoices by contract or customerDocumentNumber returns each invoice's status, paymentDate, and paymentMethod, so reminders go only to tenants whose invoice is still unpaid.

GET /invoices with contract '2045', then report the status and paymentDate of the most recent invoice

Settlement reconciliation

Finance teams reconcile what Palomma deposited against what tenants paid. GET /settlements/{date}/{cycle} returns the settlement's numberOfInvoices, amountCollected, fees, feesPostpaid, adjustments, and paymentAmount, and GET /invoices with settlementDate and settlementCycle lists the invoices included in it.

GET /settlements/2026-11-05/1, then GET /invoices with settlementDate '2026-11-05' and settlementCycle '1' and confirm the invoice amounts add up to amountCollected

Key Endpoints

4 endpoints — the palomma rentals api creates rental payment invoices for a merchant and reports how they were paid and settled.

METHOD

PATH

DESCRIPTION

POST

/invoices

Create an invoice

GET

/invoices

List invoices with filters

GET

/invoices/{id}

Get an invoice by id

GET

/settlements/{date}/{cycle}

Get a settlement by date and cycle

POST

/invoices

Create an invoice

GET

/invoices

List invoices with filters

GET

/invoices/{id}

Get an invoice by id

GET

/settlements/{date}/{cycle}

Get a settlement by date and cycle

Why Jentic?

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

Setup

Wiring Palomma by hand means bearer auth with your API key, choosing the sandbox or production host, and building invoice payloads with Colombian document types. Through Jentic you install once, import Palomma from the API Directory, store the key once, and your agent calls it.

Permission scoping

Palomma has one write, invoice creation, and three reads, so a rule can let a reconciliation agent read invoices and settlements while invoice creation stays out. The invoice id and settlement date and cycle sit in the URL path, so reads can also be pinned to one invoice or settlement.

Credential isolation

Your Palomma API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a rent invoice' or 'get a settlement', and Jentic returns the matching Palomma operation with its input schema so the agent sends the required fields.

FAQs

Specific to using Palomma Rentals API through Jentic.

What authentication does the Palomma Rentals API use?

The Palomma Rentals API uses HTTP bearer authentication per its OpenAPI spec: your Palomma API key sent as Authorization: Bearer followed by the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

What fields are required to create a Palomma invoice?

POST /invoices requires reference, amount, description, redirectUrl, and customerDocumentNumber. You can also send documentType, with values such as cc, ce, nit, or ppt, customerName, and contract to tie the invoice to a lease.

Does the Palomma Rentals API have a sandbox?

Yes. The spec lists https://sandbox.api.palomma.com/v1 alongside the production host https://api.palomma.com/v1, so you can create test invoices before going live.

How do I send a rent payment link through Jentic?

Install Jentic One, add the Palomma Rentals API from the Jentic API Directory, and store your Palomma API key once. Your agent searches for 'create a rent invoice', gets createInvoice with its input schema, calls POST /invoices, and returns the paymentUrl from the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Palomma MCP server?

You don't need an MCP server to give your agent the Palomma Rentals API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.

Can I limit what my agent is allowed to do with the Palomma Rentals API?

Yes. For a reconciliation agent, write a rule that allows only GET /invoices, GET /invoices/{id}, and GET /settlements/{date}/{cycle}: it can check payments and settlements but cannot issue new invoices. Your own Jentic One instance logs what it called.

Palomma Rentals API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbearer4 EndpointsREST

For Agents

Create a Palomma rent invoice with a payment link for a tenant, check whether and how it was paid, and read the settlement for a date and cycle with amounts collected and fees.

Use for: I need to send a rent payment link to a tenant for November, Check whether the invoice for contract 2045 has been paid, List all invoices settled on 2026-11-05, Get the settlement for yesterday's first cycle

Not supported: Does not manage leases or tenants, issue refunds, or keep accounting ledgers. Use for creating Palomma rent invoices and reading their payments and settlements only.

The Palomma Rentals API creates rental payment invoices for a merchant and reports how they were paid and settled. Creating an invoice takes a reference, amount, description, redirectUrl, and the tenant's customerDocumentNumber, with an optional documentType such as cc, ce, or nit, customerName, and contract, and the invoice returned carries a paymentUrl for the tenant to pay. Invoices can be listed by reference, contract, document number, payment date, or settlement date and cycle, and each settlement, fetched by date and cycle, reports the number of invoices, amount collected, fees, adjustments, and the payment amount. A sandbox host is available alongside production.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

25%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

69%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

33%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Palomma Rentals API to your agent

Capabilities

Start building with Palomma Rentals API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Palomma Rentals API

Jentic AI Readiness Score

Palomma Rentals API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness