Can I create a new entry with the Rentry API?

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 API?

Rentry's own documentation publishes a specific limit: anonymous entry creation is rate-limited per IP, roughly 10 per minute on rentry.co, and is configurable on self-hosted Rentry instances. Responses always come back as HTTP 200, so read the `status` value inside the JSON body: a `429` there means slow down and retry later.

How do I create a new entry through Jentic?

Install Jentic One, the self-hosted execution layer, then import Rentry from the Jentic API Directory and store its edit code once. Your agent searches for 'create a new entry', Jentic returns the matching Rentry operation with its input schema, and the call executes with the credential injected by your own instance.

How many endpoints does the Rentry API have?

Rentry exposes 5 endpoints, and all five are POST operations on a single entry: POST /new creates one, POST /edit/{url} updates its text or metadata, POST /raw/{url} returns its markdown source, POST /fetch/{url} returns its details and metadata, and POST /delete/{url} removes it. Rentry documents no other resource.

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

Yes. Because you self-host Jentic One, your own rules decide which Rentry operations and credentials the agent may use. Since Rentry puts the entry in the URL path (/fetch/{url} and /raw/{url}), you can pin the agent to fetching an entry and reading its raw markdown for a single entry, while leaving out POST /new, POST /edit/{url}, and POST /delete/{url} unless you explicitly add them. The agent can only call the operations you have allowed.

Is there a Rentry MCP server?

You do not need an MCP server to give your agent Rentry. Jentic connects it directly from the Jentic API Directory: import Rentry, store its edit code once, and your agent calls the operations you allow, with the code injected by your own Jentic One instance at execution time.

Why is there no official OpenAPI spec for Rentry?

Rentry documents its API as prose in the official radude/rentry README and ships an official Python client, but it publishes no machine-readable OpenAPI document. Probes on 2026-08-13 of rentry.co/openapi.json, /openapi.yaml and /swagger.json all returned the site's own 404 page, and the official repository's full 24-file tree contains no specification. Jentic wrote the specification this page describes and keeps it aligned with the vendor's README and client source.