Docs.

Available today

Browse Community without an account. Its public JSON manifest points to an immutable snapshot; it is a limited collection window, not a live per-user subscription API or a complete arXiv archive.

curl --fail 'https://www.datumwell.io/papers/data/manifest.json'

The manifest contains schemaVersion and snapshot. Read the named file from /papers/data/. refresh-status.json reports the last refresh attempt. An insight may be null; scheduled refresh and generated bilingual insights are not promised by this endpoint.

Accounts & keys

The original Agent docs route was /docs/api. The reviewed legacy implementation used an authenticated Clerk account to create a server-side Bearer key via POST /api/integration/key. Each key resolved to one user; topic reads and writes were scoped to that user.

• The old key format began with pt_live_. The full key was not stored; the record kept a hash, prefix and timestamps. A new key replaced the previous key for that account immediately; the complete new value was returned only when created.
• Keep keys on your agent server. Never put them in a public frontend, URL, screenshot or bot message. A browser login session is not an API key.
• Key migration and the relationship with the new Datumwell account are not configured. Do not send a legacy key to the Datumwell host.

# Legacy contract only. Replace placeholders on your own server.
API_BASE_URL='https://api.example.invalid'
AGENT_API_KEY='<YOUR_SERVER_SIDE_KEY>'
curl --fail "$API_BASE_URL/api/v1/topics" \
  -H "Authorization: Bearer $AGENT_API_KEY"

Create and manage topics

Legacy contract only. Up to five topics per account. Interest is trimmed, must contain a letter or number, and must be 3–600 characters. This topic count is a product limit, not a requests-per-minute quota.

GET/api/v1/topics

List your topic IDs.

POST/api/v1/topics

Create a topic; returns 201.

PUT/api/v1/topics/{topicId}

Update a topic you own.

DELETE/api/v1/topics/{topicId}

Delete a topic you own; returns 204.

curl --fail -X POST "$API_BASE_URL/api/v1/topics" \
  -H "Authorization: Bearer $AGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"interest":"<YOUR_RESEARCH_INTEREST>"}'

Compatibility: PUT /api/v1/subscription accepts interest (or legacy keyword) and updates the first topic, creating one if none exists. Prefer the topic-ID endpoints for multi-topic agents. The compatibility endpoint is not implemented on Datumwell.

Get papers

In the legacy service, omitting topicId returned grouped feeds for all of your topics; adding a positive integer topicId returned one owned topic. limit applied per topic: default 12, valid range 1–50.

TOPIC_ID='<YOUR_TOPIC_ID>'
curl --fail "$API_BASE_URL/api/v1/papers/latest?topicId=$TOPIC_ID&limit=5" \
  -H "Authorization: Bearer $AGENT_API_KEY"

Responses include generatedAt and either topic + papers, or topics[]. Paper fields include id, title, authors, authorDetails, abstract, insight, categories, primaryCategory, publishedAt, arxivUrl and pdfUrl. generatedAt is response time, not a guarantee of a fresh arXiv sync. Structured insight fields depend on stored content and may be unavailable.

Limits & errors

No separate per-minute quota or application-level 429 contract was found in the reviewed legacy routes. This does not establish unlimited access: hosting and upstream services may apply their own limits. Use bounded retries and honor Retry-After when supplied.

400

Invalid JSON, interest, topic ID or limit.

401

Missing, invalid or replaced Bearer key.

404

No topics, or a requested topic is not owned by the key.

409

The five-topic limit has been reached.

500

Unexpected service error; no service-level guarantee is implied.

503

The old local demo mode disables API access.

These examples document the previous implementation. No key, account or private subscription is created by reading this page. Contact Datumwell to discuss a supported integration before using a production host.