Catalogue
The classification your approvals are built on
A recipe carries the facts about somebody else's API. The hosts it answers on, how a credential is presented to it, and which paths read, write or destroy. Facts about somebody else's API go wrong more often than our own code does. So they live in data, with a schema and tests, in a repository you can read.
Published recipes
| Service | Hosts | Credential goes in | Classes |
|---|
The catalogue ships with the gateway and this build read it from the repository.
Bring a service the catalogue has never seen
An unknown host gets a conservative default and an access request with a link. The recipe can follow later, and you can write it yourself.
Connect my first agent
Free for 10,000 calls a month. No card.