canonical: https://jentic.com/apis/publons.com/publons

# Publons API

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

## For AI agents

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

## Scope

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

## Capabilities

- Submit a review
- List academics
- Get academic details

## Use cases

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

Example prompt: Call POST `/api/v2/review`/ to submit a review

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

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Reviews** — Review submission and retrieval
- **Academics** — Academic profiles and details
- **Publications** — Publication records
- **Articles** — Article details

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 60 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/publons.com/publons/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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