Update to Sugra API

{
  "description": "Work with the Sugra API over HTTPS and MCP. Use when the task needs Sugra data, a key, product directions (Finance, Macro, Entity, Net Atlas, News, Earth, Research), or which skill to load next.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 212
    }
  ],
  "name": "using-sugra-api",
  "skill_md_contents": "---\nname: using-sugra-api\ndescription: Work with the Sugra API over HTTPS and MCP. Use when the task needs Sugra data, a key, product directions (Finance, Macro, Entity, Net Atlas, News, Earth, Research), or which skill to load next.\nlicense: MIT\n---\n\n# Using the Sugra API\n\nSugra API is intelligence infrastructure: one HTTP API, one key, seven product directions. Domain-agnostic. Do not frame it through one vertical.\n\nThe surface is LLM-friendly: one `x-api-key`, one JSON envelope `{data, meta}` on most payloads (a few are flat, with `meta` or `_meta` on the record; see envelope-and-attribution), MCP as the agent-native entry. Documentation truth is https://docs.sugra.ai (search and Ask AI). This skill is a map, not the catalog.\n\nThese files are English. Reply in the user's language.\n\nPublic hedge (not a live count): 1,600+ endpoints, 160+ primary sources, 36 domains. Quote these as \"more than\", never as an exact figure. The current operation list is `https://sugra.ai/openapi.json` (skill `live-docs`).\n\n## Two complete ways in\n\n| Surface | When | How |\n|---|---|---|\n| HTTPS `https://sugra.ai` | The agent can GET/POST | `x-api-key` on `/api/v1/...` |\n| MCP | The host is an MCP client | the Sugra API MCP server; setup for each client: https://docs.sugra.ai/doc-2263382 |\n\nBoth reach the same API. Use the surface the host already has, or the one the user named. Key: sign up at https://app.sugra.ai/register (a key is issued at signup), manage keys at https://app.sugra.ai/developer/keys. Free: 50 requests a day per account. Do not log the key.\n\n## Before quoting a figure\n\nA call that returns data is not yet an answer. Check that `meta.endpoint` is the operation meant, and that the place, entity, period, and measure in `data` are the ones the user asked about. An optional parameter left out takes its default, which can be another country or period; a required one must be set. Details: skill `discover-and-call`.\n\n## Seven directions (one key, one budget)\n\n| Direction | Coverage |\n|---|---|\n| Sugra Finance | Equities, fundamentals, filings, fixed income, derivatives, crypto, forex |\n| Sugra Macro | Central banks, national statistics, FRED, IMF, World Bank, OECD |\n| Sugra Entity | Company resolution, sanctions and watchlist screening, identifiers |\n| Sugra Net Atlas | Internet infrastructure: ASNs, prefixes, IXPs, routing, DNS |\n| Sugra News | Global news flow and event signals |\n| Sugra Earth | Weather, hazards, energy, transport, air quality, climate |\n| Sugra Research | Scientific, patent, and academic datasets |\n\n## Skill map\n\n| Need | Skill |\n|---|---|\n| Live docs, search, Ask AI, sources, blog | `live-docs` |\n| Key, plans, quota, errors | `auth-and-quota` |\n| Find, call, and check an operation (HTTP and MCP) | `discover-and-call` |\n| Envelope, sources, clocks, MCP shaping | `envelope-and-attribution` |\n| Two or three directions in one answer | `cross-domain-briefing` |\n"
}