Developer access · Field notes
“Unknown API” does not mean “no API”
Separate missing evidence, an integration claim, and a documented interface before making an architectural decision.
Absence is a claim too
A missing developer page may reflect an invite-only program, a poorly indexed website, a partner integration, or a product without an external API. Search results alone do not distinguish those cases. In startidea, Unknown means we have not verified availability. It should prompt a question, not close the shortlist.
An integration logo is not an API contract
A vendor can connect to another product without exposing an interface you can use. Even an “API available” sentence leaves access terms, supported operations, authentication, rate limits, and version policy unresolved. Save the exact claim and its source. Ask for documentation or a sandbox for the operation your application needs.
Read the interface, then test access
Boston Dynamics publishes Spot developer documentation organized around robot capabilities and service concepts. The existence of such documentation is a stronger discoverable signal than a generic integration page. It still does not establish that a particular buyer has the equipment, permissions, commercial rights, or deployment conditions required to use every operation. Public docs and granted access are different facts.
Write a one-operation acceptance test
For an invoice workflow, that might be “create a draft invoice with an external reference, retrieve it, then repeat the request safely.” Use disposable data and authorized credentials. Record request and response examples without secrets. If the only available interface cannot preserve your external identifier or recover from a timeout, “has an API” is too coarse a conclusion.
Sources & scope
Prepared October 13, 2026 with AI assistance. Vendor descriptions are attributed claims. Worksheets are proposed methods; numerical examples are illustrative. No hands-on vendor testing is represented.