# EDGAR Going-Concern Status Lookup

> EDGAR Going-Concern Status Lookup is a paid API for AI agents from oracles-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Retrieves stored going-concern filing status details for a specific SEC EDGAR entity by its filing entityId.

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/edgar-going-concern/status
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edgar-going-concern-status-lookup-2fdd211a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vMo08BHkhqWxlJCV7WrxW

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability edgar-going-concern-status-lookup-2fdd211a
```

Example prompt: Can you check the going-concern status for the Apple SEC EDGAR filing with ID 'edgar:0000320193-26-000064'?

## When to prefer this

Use this endpoint when you need to quickly check the going-concern audit opinion status for a specific SEC-filing entity identified by its EDGAR entityId. Prefer this over raw SEC EDGAR scraping when you want a pre-processed, structured going-concern flag without parsing full filings.

## Known failure modes

- Missing or invalid entityId returns no record or error
- EntityId not tracked by the oracle returns empty result
- Malformed entityId format causes lookup failure
- Service unavailable returns HTTP 5xx
- Payment not processed returns HTTP 402

## How this service works

Full stored detail for a single SEC EDGAR going-concern warnings filing by accession number (entityId like 'edgar:0000320193-26-000064') — company name, CIK, form type, filing date, and a direct link to the filing index.

## Output

Returns a stored entity record containing going-concern filing details for the specified EDGAR entityId, including entity metadata and status fields indicating whether a going-concern opinion was disclosed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string",
       "description": "entityId to look up; omit to list tracked entities"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "entity": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/edgar-going-concern-status-lookup-2fdd211a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracles-production.up.railway.app](https://www.zero.xyz/host/oracles-production.up.railway.app/llms.txt)