Rentry

Name: Rentry API
Brand: Rentry
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey5 EndpointsREST

For Agents

Programmatically create a new entry, edit an existing entry. Covers 5 operations with apiKey authentication.

Use for: I need to a new entry, I want to edit an existing entry, Search for raw markdown text of an entry, Find all fetch entry details including metadata

Install Jentic One Beta

Connect the Rentry to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rentry, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Rentry API.

Create a new entry

Edit an existing entry

Get raw markdown text of an entry

Fetch entry details including metadata

GET STARTED

Start building with Rentry API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Rentry API for, with concrete tasks.

★ Developer Tools Operations

Use the Rentry to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including create a new entry, edit an existing entry, get raw markdown text of an entry.

Call POST /new to create a new entry

Automated Entries Management

Automate entries operations by combining multiple Rentry endpoints. Agents can edit an existing entry and then get raw markdown text of an entry in a single workflow.

Call POST /edit/{url} to edit an existing entry, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rentry 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 apiKey tokens manually.

Search Jentic for 'create a new entry', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — rentry.

METHOD

PATH

DESCRIPTION

POST

/new

Create a new entry

POST

/edit/{url}

Edit an existing entry

POST

/raw/{url}

Get raw markdown text of an entry

POST

/fetch/{url}

Fetch entry details including metadata

POST

/delete/{url}

Delete an entry

POST

/new

Create a new entry

POST

/edit/{url}

Edit an existing entry

POST

/raw/{url}

Get raw markdown text of an entry

POST

/fetch/{url}

Fetch entry details including metadata

POST

/delete/{url}

Delete an entry

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Rentry apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a new entry') and Jentic returns the matching Rentry operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Rentry integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 Rentry API through Jentic.

What authentication does the Rentry use?

The Rentry uses an API key passed in the `csrftoken` cookie. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create a new entry with the Rentry?

Yes. Use the POST /new endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Rentry?

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 create a new entry through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new entry'. Jentic returns the matching Rentry operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Rentry have?

The Rentry exposes 5 endpoints covering entries operations.