Install Jentic One Beta

Connect the Filebase IPFS Pinning Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Filebase IPFS Pinning Service 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%2Ffilebase.com%2Ffilebase" | 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%2Ffilebase.com%2Ffilebase" | 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 Filebase IPFS Pinning Service API.

Pin an existing IPFS CID into a Filebase IPFS bucket

List pin requests and filter them by status

Get a pin request and poll its status until it is pinned or failed

Replace the CID behind an existing pin request

Remove a pin request to stop pinning that content

GET STARTED

Start building with Filebase IPFS Pinning Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Filebase IPFS Pinning Service API for, with concrete tasks.

★ Agent-managed IPFS pinning through Jentic

An AI agent pins a CID produced elsewhere, receives a request handle, and polls it until the status turns pinned, so content stays reachable on IPFS without a person watching the queue. Because pinning is asynchronous, the agent can pin a batch, then revisit each request's status and retry any that failed.

Pin a given CID into a Filebase bucket, then poll the returned request until its status is pinned or failed

Keep published content reachable

Apps that reference content by CID need that content to stay available. The API pins the CID into a Filebase bucket and reports when the pin is complete, so a publishing workflow can confirm durability before it hands a gateway link to users, and unpin content it no longer needs.

List pin requests filtered to failed status and replace each one with its intended CID

Audit and clean up pins

Over time a bucket accumulates pins that are no longer referenced. The API lists pin requests and their statuses so an agent can report what is pinned, then remove the requests that are stale, freeing paid storage without touching content that is still in use.

List all pin requests, identify ones not in an active set, and remove each stale pin request

Key Endpoints

5 endpoints — the filebase ipfs pinning service api pins existing ipfs content by cid into a filebase ipfs bucket and tracks each pin request through to completion.

METHOD

PATH

DESCRIPTION

GET

/pins

List pin requests

POST

/pins

Pin an existing CID

GET

/pins/{requestid}

Get a pin request and its status

POST

/pins/{requestid}

Replace a pin request

DELETE

/pins/{requestid}

Remove a pin request

GET

/pins

List pin requests

POST

/pins

Pin an existing CID

GET

/pins/{requestid}

Get a pin request and its status

POST

/pins/{requestid}

Replace a pin request

DELETE

/pins/{requestid}

Remove a pin request

Why Jentic?

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

Setup

Wiring the Filebase pinning API by hand means generating a bucket-specific Bearer token, handling the asynchronous poll until a pin is complete, and remembering the request handle is opaque rather than a CID. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

A Filebase token is already scoped to one bucket, and on top of that you choose which operations your agent may call, so it can add and list pins while the replace and remove operations stay out unless you add them.

Credential isolation

Your Filebase bucket 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 'pin an IPFS CID' or 'check a pin's status', and Jentic returns the matching Filebase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Filebase IPFS Pinning Service API through Jentic.

What authentication does the Filebase IPFS Pinning Service API use?

It uses a bucket-specific Bearer token sent in the Authorization header, generated in the Filebase console, per its OpenAPI spec. Because the token is tied to one bucket, a call only ever touches that bucket's pins, and a paid account is required.

How do I know when a pin is complete with the Filebase API?

Pinning is asynchronous. Creating or replacing a pin returns a request with an opaque identifier, and you poll that request until its status reads pinned or failed. Keep the source content reachable until the status is pinned, because the service fetches the CID during that window.

What are the rate limits for the Filebase IPFS Pinning Service API?

The OpenAPI spec does not state a request rate limit. A paid account is required, and limits track your plan, so check the Filebase documentation for the current ceilings before pinning at scale.

Is there a Filebase MCP server?

You don't need an MCP server to give your agent the Filebase pinning API. Jentic connects it directly from the API Directory: import it, store your bucket token once, and your agent calls the pin, status, replace, and remove operations on demand.

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

Yes. A Filebase token is already scoped to one bucket, and on top of that you can write a rule that allows only the add-pin and list operations, leaving the replace and remove operations off unless you add them, so an agent can pin and report without unpinning anything. Every call it makes is recorded in your Jentic One audit log.

How do I pin a CID with the Filebase API through Jentic?

Search Jentic for 'pin an IPFS CID', add the Filebase IPFS Pinning Service API from the directory, and store your bucket token once; your agent then pins the CID and polls the returned request until it is complete. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Filebase IPFS Pinning Service API

AI ReadinessAI-Ready (A-)79/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject Storagebearer5 EndpointsREST

For Agents

Pin existing IPFS content by CID into a Filebase bucket, list and poll pin requests until they are pinned or failed, and replace or remove a pin. Works against the IPFS Pinning Service standard.

Use for: Pin an IPFS CID in my Filebase bucket, Check the status of a pin request, List all my pin requests that are still pinning, Replace the content behind a pin request with a new CID

Not supported: Does not handle file upload, gateway serving, or IPFS content creation. Use for pinning existing IPFS content by CID into a Filebase bucket only.

The Filebase IPFS Pinning Service API pins existing IPFS content by CID into a Filebase IPFS bucket and tracks each pin request through to completion. Pinning is asynchronous: creating or replacing a pin returns a request you poll until its status is pinned or failed, keeping the source content reachable in the meantime. A bucket-specific Bearer token authorises each call and a paid account is required. The request identifier it returns is an opaque handle, not a CID or a UUID, and any content pinned on IPFS is public to anyone who has the CID.

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

64%

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: B+Signals: 4

89%

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.

89%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Filebase IPFS Pinning Service API to your agent

Capabilities

Start building with Filebase IPFS Pinning Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Filebase IPFS Pinning Service API

Jentic AI Readiness Score

Filebase IPFS Pinning Service 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