Install Jentic One Beta

Connect the Publons API to your agent

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

Submit a review

List academics

Get academic details

Use Cases

Patterns agents use Publons API for, with concrete tasks.

★ Developer Tools Operations

Use the Publons API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including submit a review, list academics, get academic details.

Call POST /api/v2/review/ to submit a review

GET STARTED

Start building with Publons API

Explore with Jentic One

View OpenAPI Document

Automated Reviews Management

Automate reviews operations by combining multiple Publons API endpoints. Agents can list academics and then get academic details in a single workflow.

Call GET /api/v2/academic/ to list academics, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Publons API 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 apiKey tokens manually.

Search Jentic for 'submit a review', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — access reviews, academics, publications, and articles from the publons platform (web of science).

METHOD

PATH

DESCRIPTION

POST

/api/v2/review/

Submit a review

GET

/api/v2/academic/

List academics

GET

/api/v2/academic/{identifier}/

Get academic details

GET

/api/v2/academic/review/

List academic reviews

GET

/api/v2/academic/review/{id}/

Get review details

GET

/api/v2/academic/publication/

List academic publications

GET

/api/v2/academic/publication/{id}/

Get publication details

GET

/api/v2/article/{id}/

Get article details

POST

/api/v2/review/

Submit a review

GET

/api/v2/academic/

List academics

GET

/api/v2/academic/{identifier}/

Get academic details

GET

/api/v2/academic/review/

List academic reviews

GET

/api/v2/academic/review/{id}/

Get review details

GET

/api/v2/academic/publication/

List academic publications

GET

/api/v2/academic/publication/{id}/

Get publication details

GET

/api/v2/article/{id}/

Get article details

Why Jentic?

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

Setup

Wiring the Publons API by hand means setting your token in the Authorization header and tracking academic, review, and publication ids across calls yourself. Through Jentic you install once, import Publons from the API Directory, store the token once, and your agent calls it.

Permission scoping

Publons puts the record id in the URL path (/api/v2/academic/{identifier}/, /api/v2/academic/review/{id}/), so a rule can pin your agent to reading a specific academic or review. You choose the operations it may call, so writes like submitting a review are not included unless you add them.

Credential isolation

Your Publons API 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 'look up an academic' or 'read a review', and Jentic returns the matching Publons operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Publons API through Jentic.

What authentication does the Publons API use?

The Publons API uses an API key passed in the `Authorization` header. 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 submit a review with the Publons API?

Yes. Use the POST /api/v2/review/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Publons API?

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 submit a review through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit a review'. Jentic returns the matching Publons API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Publons API have?

The Publons API exposes 8 endpoints covering reviews, academics, publications operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Publons operations and credentials your agent may use, so you can allow read calls like GET /api/v2/academic/ or GET /api/v2/academic/review/ while excluding the write path POST /api/v2/review/. Since Publons puts the record id in the URL path, such as /api/v2/academic/{identifier}/ and /api/v2/academic/review/{id}/, a rule can pin the agent to reading one specific academic or review. Submitting a review is never included unless you explicitly add that operation.

Publons API

Name: Publons API
Brand: Publons API
Availability: InStock

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey8 EndpointsREST

For Agents

Programmatically submit a review, list academics. Covers 8 operations with apiKey authentication.

Use for: I need to submit a review, I want to academics, Search for academic details, Find all academic reviews

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Access reviews, academics, publications, and articles from the Publons platform (Web of Science). The API exposes 8 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

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.

50%

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

62%

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.

50%

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

50%

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 Publons API to your agent

Capabilities

Use Cases

Start building with Publons API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Publons API

Jentic AI Readiness Score

Publons 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