eigenised-news-paid-research

name	eigenised-news-paid-research
description	Use the eigenisedNews paid research API from an autonomous agent. Covers discovery, x402/MPP payment retry flow, endpoint calls, and EigenCompute verification.

eigenisedNews Paid Research API

Use this skill when an agent needs to research a news article through the paid eigenisedNews API. The endpoint accepts either x402 (Base USDC) or MPP (Tempo USDC) payment credentials through dual402.

Required inputs

• EIGENISED_NEWS_BASE_URL — deployed service origin. Use https://eigenised-news.vercel.app
• An x402-compatible wallet/client, or an MPP-compatible Tempo client.
• A public HTTP(S) news article URL.

Discovery endpoints

Fetch these before paying:

curl "$EIGENISED_NEWS_BASE_URL/verify"
curl "$EIGENISED_NEWS_BASE_URL/openapi.json"
curl "$EIGENISED_NEWS_BASE_URL/.well-known/x402"

Check that /verify reports payment.enabled=true, the expected x402 payee, the MPP recipient, and the EigenCompute dashboard URL.

Paid request flow

Canonical endpoint:

POST /api/research
content-type: application/json

{"articleUrl":"https://example.com/news/story"}

1. Send the request once without payment.
2. Expect HTTP 402 Payment Required.
3. Read PAYMENT-REQUIRED and WWW-Authenticate; they advertise both x402 and MPP challenges.
4. Pay using either protocol.
5. Retry the exact same method, URL, query string, and JSON body with the payment credential attached.

Example challenge probe:

curl -i "$EIGENISED_NEWS_BASE_URL/api/research" \
  -H 'content-type: application/json' \
  -d '{"articleUrl":"https://example.com/news/story"}'

For x402 clients, attach the credential in the Payment-Signature header or the client’s supported x402 header. For MPP clients, follow the MPP challenge in WWW-Authenticate.

Response contract

Successful paid responses contain:

• article — fetched URL, content hash, byte length, and fetch status.
• proPrompt / contraPrompt — prompts generated by the main planner agent.
• proAnalysis / contraAnalysis — the two research perspectives.
• mainSummary — main-agent comparison summary over the pro/contra final verdicts and analyses.
• promptBindings and agentRuns — prompt hashes and model run metadata.
• manifest and signature — signed EigenCompute/verifiable research manifest.
• raw — null by default; add ?include=raw for exact planner/pro/contra/summary prompts and raw outputs.

Use POST /api/research?include=raw only when you need strict audit evidence; it returns larger payloads.

Verification checklist

Before trusting a response:

1. Confirm GET /verify payment metadata matches the expected deployment.
2. Confirm manifest.kind === "research".
3. Confirm the article URL and content hash in manifest.article match response.article.
4. Confirm signature is present and starts with 0x.
5. If strict audit is needed, request ?include=raw and run the repository verifier against the saved response.

Failure handling

• 402 — no valid payment yet; pay and retry.
• 400 — invalid request body or article URL.
• 502 / 504 — article fetch, model, or upstream gateway issue; retry if retryable=true.
• payment_settle_failed — x402 verification passed but settlement failed; do not treat the research response as paid.