Install Jentic One Beta

Connect the Peptide Library API to your agent

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

Search peptide profiles by text, category, research_area, evidence_level such as clinical-trial or preclinical, or regulatory_status

Read a peptide's research summary, the studies its profile cites, and its regulatory status by slug

Filter the study index by peptide, evidence_classification, year_from and year_to, or text, sorted newest or oldest

List vendors by country, ships_to destination, product_category, or min_rating, and compare several vendors side by side

GET STARTED

Start building with Peptide Library API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Peptide Library API for, with concrete tasks.

★ Research assistant agent through Jentic

A research or education agent finds the Peptide Library search and profile operations through Jentic, looks up a peptide by slug, and answers with its evidence level, regulatory status, and cited studies rather than general web content. The research endpoints work without a key, and for keyed calls Jentic injects the credential at call time. The API returns no dosing or administration content, which keeps the agent's answers in the research and education scope the API states.

Call GET /peptides with search 'semaglutide', then GET /peptides/{slug}/research and GET /regulatory-status/{slug} for the top result and summarise the evidence level and status

Literature review by evidence level

GET /studies filters the cited literature by peptide, evidence_classification, publication year range, and text, with cursor pagination and sorting by newest, oldest, or title. Combined with GET /peptides filtered by evidence_level, a reviewer can separate peptides with human trial evidence from those supported only by preclinical work.

Call GET /studies with peptide set to the profile slug, year_from 2020, and sort 'newest', then list each study's title and evidence classification

Vendor and price comparison for researchers

With a key holding the vendors:read and pricing:read scopes, GET /prices/compare returns last-seen offers for one peptide filtered by form, currency, ships_to, and in_stock, and GET /vendors/compare compares chosen vendors for a destination. Prices are shown as last seen on the vendor's site and are never converted between currencies, so a lab can shortlist suppliers and then confirm on the vendor's site.

Call GET /prices/compare with peptide set to the profile slug, currency 'EUR', ships_to 'DE', and in_stock true, then GET /vendors/compare with the ids of the three cheapest vendors

Key Endpoints

22 endpoints — the peptide library api serves peptide research profiles, the scientific studies they cite, regulatory status, and vendor, product, and price listings from peptide library, for research and education only.

METHOD

PATH

DESCRIPTION

GET

/peptides

List and search peptides

GET

/peptides/{slug}/research

Research summary for a peptide

GET

/regulatory-status/{slug}

Regulatory status of a peptide

GET

/studies

List studies

GET

/vendors

List vendors

GET

/prices/compare

Compare prices for a peptide

GET

/search

Search peptides and educational content

GET

/peptides

List and search peptides

GET

/peptides/{slug}/research

Research summary for a peptide

GET

/regulatory-status/{slug}

Regulatory status of a peptide

GET

/studies

List studies

GET

/vendors

List vendors

GET

/prices/compare

Compare prices for a peptide

GET

/search

Search peptides and educational content

Why Jentic?

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

Setup

Wiring Peptide Library by hand means choosing between its bearer and X-API-Key forms, requesting the right scopes for vendor and price calls, and following cursor pagination yourself. Through Jentic you install once, import Peptide Library from the API Directory, store the key once, and your agent calls it.

Permission scoping

Peptide Library puts the peptide slug and vendor id in the URL path (/peptides/{slug}/... and /vendors/{id}/...), so a rule can pin your agent to one peptide's profile or one vendor's listings. You choose the operations it may call, so an agent meant for research questions does not get vendor, product, or price listings unless you add them.

Credential isolation

Your Peptide Library 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 'look up peptide research' or 'compare peptide vendor prices', and Jentic returns the matching Peptide Library operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Peptide Library API through Jentic.

What authentication does the Peptide Library API use?

Per its OpenAPI spec, the Peptide Library API accepts an API key either as an HTTP bearer token (`Authorization: Bearer pl_live_...`) or in the `X-API-Key` header. Research and study endpoints are declared with an optional key and work anonymously at a per-IP limit, while vendor, product, and price endpoints require a key with the matching scope, such as vendors:read, products:read, or pricing:read. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Does the Peptide Library API give dosing information?

No. The API describes itself as research and educational information only, not medical advice and not a recommendation to buy or use any substance. It states that it never returns dose figures, regimens, reconstitution, or injection instructions.

How do I look up a peptide's research through Jentic?

Search Jentic for 'look up peptide research', call GET /peptides with a search term to find the profile slug, then call GET /peptides/{slug}/research and GET /peptides/{slug}/studies for its summary and cited studies. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the Peptide Library API?

The OpenAPI spec states that keyed vendor, product, and price requests count against your plan's per-minute and monthly limits, with the Free Developer plan at 60 per minute and 5,000 per month. Responses carry RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers, over-limit calls return 429 with Retry-After, and anonymous requests are limited per IP address.

Is there a Peptide Library MCP server?

You don't need an MCP server to give your agent the Peptide Library API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

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

Yes. Every operation is a read, so the choice is which data the agent may see. For example, allow only GET /peptides, GET /peptides/{slug}/research, GET /peptides/{slug}/studies, and GET /studies, so an education agent answers from research profiles and literature and never queries vendor, product, or price listings. Every call it makes is logged by your Jentic One instance.

Peptidelibrary App Peptide Library API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareClinical Databearer, apiKey22 EndpointsREST

For Agents

Look up peptide research profiles, cited studies, and regulatory status for research and education, and, with a scoped key, compare vendors and last-seen prices by form, currency, and shipping destination.

Use for: Find peptides with clinical-trial level evidence in the longevity category, Get the regulatory status of semaglutide, List studies on a peptide published since 2020, Retrieve the research summary for a peptide profile

Not supported: Does not provide medical advice, dosing or administration instructions, or ordering and checkout. Use for peptide research profiles, studies, regulatory status, and vendor price listings for research and education only.

The Peptide Library API serves peptide research profiles, the scientific studies they cite, regulatory status, and vendor, product, and price listings from Peptide Library, for research and education only. Research and study endpoints let you search peptides by category, research area, evidence level, or regulatory status, read a profile's research summary and cited studies, and filter the study index by year, evidence classification, or text. Keyed vendor, product, and price endpoints list vendors with shipping destinations and ratings, compare vendors, and compare last-seen prices for a peptide by form, currency, and destination. The API states that it is not medical advice and never returns dose figures, regimens, reconstitution, or injection instructions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

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

37%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

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

51%

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

55%

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

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Peptide Library API to your agent

Capabilities

Start building with Peptide Library API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Peptidelibrary App Peptide Library API

Jentic AI Readiness Score

Peptide Library 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