Install Jentic One Beta

Connect the Raindrop.io API to your agent

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

Get root collections

Reorder all collections

Remove multiple collections

Merge collections

Create collection

Use Cases

GET STARTED

Start building with Raindrop.io API

Explore with Jentic One

View OpenAPI Document

Automated Collections Management

Automate collections operations by combining multiple Raindrop API (Unofficial) endpoints. Agents can reorder all collections and then remove multiple collections in a single workflow.

Call PUT /collections to reorder all collections, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Raindrop API (Unofficial) 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 bearer, oauth2 tokens manually.

Search Jentic for 'get root collections', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

48 endpoints — **unofficial** openapi specification of raindrop api.

METHOD

PATH

DESCRIPTION

GET

/collections

Get root collections

PUT

/collections

Reorder all collections

DELETE

/collections

Remove multiple collections

GET

/collections/childrens

Get child collections

PUT

/collections/merge

Merge collections

PUT

/collections/clean

Remove all empty collections

POST

/collection

Create collection

GET

/collection/{id}

Get collection

GET

/collections

Get root collections

PUT

/collections

Reorder all collections

DELETE

/collections

Remove multiple collections

GET

/collections/childrens

Get child collections

PUT

/collections/merge

Merge collections

PUT

/collections/clean

Remove all empty collections

POST

/collection

Create collection

GET

/collection/{id}

Get collection

Why Jentic?

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

Setup

Wiring Raindrop.io by hand means learning its bearer and OAuth2 flows and hand-coding requests across its collections, raindrops, and tags endpoints. Through Jentic you install once, import the Raindrop.io API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Raindrop puts the collection id in the URL path (/collection/{id}), so a rule can pin your agent to one collection: it can read and update items in that collection and nothing else. You choose the operations it may call, so destructive ones like deleting a collection or emptying the trash are not included unless you add them.

Credential isolation

Your Raindrop token 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 'list my bookmark collections' or 'save a new raindrop', and Jentic returns the matching Raindrop operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Raindrop.io API through Jentic.

What authentication does the Raindrop API (Unofficial) use?

The Raindrop API (Unofficial) uses bearer, oauth2 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 get root collections with the Raindrop API (Unofficial)?

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

What are the rate limits for the Raindrop API (Unofficial)?

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 get root collections through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get root collections'. Jentic returns the matching Raindrop API (Unofficial) operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Raindrop API (Unofficial) have?

The Raindrop API (Unofficial) exposes 48 endpoints covering collections, sharing, raindrops operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Raindrop operations and which stored token the agent may use. Since Raindrop puts the collection id in the URL path, such as /collection/{id}, you can pin the agent to a single collection so it only reads and updates items there and nothing else. You also choose the operations it may call, so destructive ones like deleting a collection or emptying the trash stay out of reach unless you explicitly add them.

Raindrop.io API

Name: Raindrop.io API
Brand: Raindrop API (Unofficial)
Availability: InStock

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageBackup Recoverybearer, oauth248 EndpointsREST

For Agents

Programmatically get root collections, reorder all collections. Covers 48 operations with bearer, oauth2 authentication.

Use for: I need to root collections, I want to reorder all collections, Search for remove multiple collections, Find all child collections

Not supported: Does not handle payments, communications, or crm - use for storage and databases only.

**UNOFFICIAL** OpenAPI specification of Raindrop API. This OpenAPI spec has been made by hand with reference to official documentation because it is not provided by Raindrop.io. Because official documentation not maintained well, there are very (highly) likely to have mismatch in schemas. As we can't inspect and address all issues, schema being updated as we find issues. Any contributions are welc. The API exposes 48 endpoints secured with bearer, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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).

25%

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: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

28%

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: DSignals: 4

19%

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.

59%

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: A-Signals: 1

75%

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: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Raindrop.io API to your agent

Capabilities

Use Cases

Start building with Raindrop.io API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Raindrop.io API

Jentic AI Readiness Score

Raindrop.io 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