Conclusion: choosing and combining Sugra directions

Series: close
Prerequisites: Platform intro and any direction articles you need
Auth reminder: one x-api-key, volume-only plan gates

This article closes the series. It is a decision guide, not a new API surface.

---

What you should take away

1. One product, seven directions - same host, same key, same general envelope (with NetAtlas _meta as the main shape exception).
2. Each direction is deep enough alone - articles 1-7 are full maps with use cases, not blurbs.
3. Composition is client-side - articles 8-11 show call sequences and failure handling; Sugra does not hide a blackbox multi-domain score.
4. Provenance is the product feature - meta.source, meta.data_time, Entity disclaimers, Earth attribution, NetAtlas atlas build time.
5. Limits are volume - budget calls; batch carefully; handle 429 and 503.

---

Decision guide: which direction first?

If your question is…	Start with
Price, indicators, 13F, crypto/FX board	Finance
CPI, policy rates, official GDP, curve	Macro
Sanctions / KYB / wallet screen	Entity
IP / ASN / RPKI / Tor / CT	NetAtlas
Headlines, media volume/tone, attention	News
Weather, hazards, grid, METAR	Earth
Papers, DOI, long-run GDP, NBER	Research
Auth, envelope, quotas	Platform intro

---

When to compose

Need	Composition article
Official regime + market print	08 Macro + Finance
Screen + media context	09 Entity + News
Ops weather + hazards + grid (+ METAR)	10 Earth ops
Name event pack: market + media + macro backdrop	11 Event stack

Rules of thumb:

• Prefer one direction until you need a second answer type.
• Cache slow legs (Macro releases, Entity list freshness checks).
• Never invent a combined “score” without publishing the formula and disclaimers.
• Entity + anything else still ends with signal, not determination.
• Finance + anything else still ends with not investment advice.

---

Full series map

Foundation and overviews

0. Platform intro
1. Finance
2. Macro
3. Entity
4. NetAtlas
5. News
6. Earth
7. Research

Compositions

8. Macro + Finance
9. Entity + News
10. Earth ops
11. Event stack

Close

12. This conclusion

---

Integration checklist

• Key only in env / secret store
• Read X-RateLimit-* on a probe call
• Parse data + meta (and NetAtlas _meta)
• Show meta.source / data_time in UI or agent citations
• Entity disclaimer visible when screening
• Finance / market-adjacent copy: not investment advice
• 429 and 503 handlers with backoff / last-good cache
• Live path checks (13F /{cik}/holdings, forex /latest, METAR /api/v2/transport/aviation/metar)

---

Where to build next

Resource	URL / location
Get a key	https://app.sugra.ai
Family overview	https://sugra.systems/api/family
Runnable recipes	https://github.com/Sugra-Systems/sugra-api-cookbook
Hosted MCP (agent UI users)	https://app.sugra.ai/mcp
This series folder	README

---

Read next

• Back to the start: Platform intro
• Jump to a direction you skipped
• Open the cookbook and run 01_quickstart.py with your key

Thank you for reading the series end to end - or for using the TOC to take only what you need. The API is one key; the articles stay modular on purpose.