🧭 TOPICS

API discovery

Evidence, specifications, and useful endpoint records.

API discovery is the starting point for several different jobs: planning an integration, giving an IDE better context, extracting a structured record, or designing a page from real fields. This topic brings those jobs together without pretending they have the same output.

Look for the recurring distinction between a published contract, a runtime observation, and an application decision. Keeping those evidence types separate makes it easier to review a catalog and explain where a claim came from. A sample response should not silently become a guarantee.

Choose a guide below based on the decision you need to make. The catalog documentation is a practical companion: it shows a small record with explicit uncertainty and an execution boundary. For a complete introduction, start with API foundations, then return here to explore how reviewed discovery supports the rest of the workflow.

4 field notes in this topic