PMIC Pharma Safety and Approval Signals

health

Serving

Scored drug-market and company safety briefs from openFDA, FDA, BLS and ClinicalTrials.gov: recalls, adverse events, approvals, trial pipelines, shortages, device safety, warning letters and drug prices, for the US market and for Pfizer, Lilly and J&J. Each is a 0-100 score with drivers and citations. POST /v1/brief with {vertical}. Research signal, not medical or investment advice.

Endpoint: POST https://agent.pocket.network/v1/pmic-pharma-signals/v1/brief
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/pmic-pharma-signals/v1/brief \
  -H 'content-type: application/json' \
  -d '{"vertical":"drug-market","entity_id":"pfe","horizon":"7d"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods PMIC Pharma Safety and Approval Signals accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/brief`	read
`POST /v1/catalog`	read
`POST /v1/events`	read
`POST /v1/explain`	read
`POST /v1/overview`	read
`POST /v1/signal`	read
`POST /v1/signals`	read
`POST /v1/verticals`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "The body of POST /v1/brief; company-safety and clinical-pipeline also need entity_id. The other routes take JSON bodies too: /v1/verticals takes {}; /v1/overview takes entity_id and horizon; /v1/signals takes source_id, horizon, sort, direction, min_confidence and limit; /v1/signal and /v1/explain take series_id; /v1/catalog takes entity_id and q; /v1/events takes entity_id, event_type, severity, since and limit.",
  "properties": {
    "vertical": {
      "type": "string",
      "enum": [
        "drug-market",
        "company-safety",
        "clinical-pipeline",
        "drug-shortages",
        "device-safety",
        "drug-prices",
        "fda-enforcement"
      ],
      "description": "Which brief to score."
    },
    "entity_id": {
      "type": "string",
      "enum": [
        "pfe",
        "lly",
        "jnj"
      ],
      "description": "The drug maker, for the company verticals."
    },
    "horizon": {
      "type": "string",
      "enum": [
        "7d",
        "30d",
        "90d",
        "365d"
      ],
      "description": "The window the trend is measured over."
    }
  },
  "required": [
    "vertical"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/brief, a JSON object with vertical, title, status, score (0-100), label, trend, summary, drivers, risk_flags, confidence, inputs, watch and citations. Bad input answers 400 with `{ error: { code, message } }`."
}