canonical: https://jentic.com/apis/peptidelibrary.app/peptidelibrary # Peptidelibrary App Peptide Library API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Compare last-seen prices for one peptide by form, currency, ships_to, and in_stock - Browse a vendor's products and prices, filtered by strength_min_mg and strength_max_mg or price range ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Research** — Peptide profiles, research summaries, regulatory status, categories, and research areas - **Studies** — The study index and the studies cited by each profile - **Vendors** — Vendors with ratings, shipping destinations, products, prices, and comparison - **Products and prices** — Product listings and last-seen prices with price comparison per peptide ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 82 / 100 - **View full report:** https://jentic.com/apis/peptidelibrary.app/peptidelibrary/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **NCBI Datasets API** — NCBI genome, gene, and taxonomy datasets - **openFDA Drug API** — FDA drug labels, adverse events, and recalls - **ClinicalTrials.gov API** — Registry of clinical studies and their status - **OpenAlex API** — Open index of scholarly works, authors, and citations ## FAQ ### 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.