Works out what you meant
Not just what was typed. What the request is really after is written down before anything else happens, and it is what we come back to at the end.
API Access Point sits between your product and the machinery that makes it smart. Your app asks for an outcome — a summary, a reply, a judgement — and we take care of everything between the asking and the answer, including reading it back before your user ever sees it.
Every request is read for what it is actually asking, matched to a hand that suits it, and checked on the way back out. You see one address and one answer; the deciding happens on our side of the door.
Not just what was typed. What the request is really after is written down before anything else happens, and it is what we come back to at the end.
Some questions want speed, some want patience, and most want neither more than they want to be right. Picking well is the whole job.
The answer is held up against what was asked for in the first place, so something that missed the point arrives labelled as such instead of quietly.
Send something your product might ask for. This is a real call to the real endpoint — no key, no signup — and underneath the answer is the gateway’s own account of what it decided, what the alternatives would have cost, and where the milliseconds went.
Pick one and send it. What comes back is a real call to the real endpoint, with the gateway’s own account of what it decided underneath.
The key behind this page is held to $2 a day, one origin, one capability and the cheapest tier — by the same pre-flight check that governs a paying tenant. When the day’s budget runs out the page says so and shows a trace captured earlier, rather than quietly becoming something else.
It is an ordinary web request, so anything that can make one is a first-class citizen. Nothing needs a kit installed, and nothing needs a secret it should not be holding.
What a customer gets is something you set, not something you deploy. Adjust it on a Tuesday afternoon and it is true on a Tuesday afternoon.
An app carries a key that only works from where you said it would. Changing anything behind it is our afternoon, not an app store review.
Point as many at it as you like. What they are collectively allowed to spend is settled at the door, so busy never quietly turns into expensive.
curl -X POST https://api.apiaccesspoint.com/v1/ask \ -H "Authorization: Bearer $YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "job": "reply-to-customer", "ask": "They cannot find their invoices." }' # One address. It does not move, and it does not # care what we changed behind it this morning.
Nobody loses sleep over the things that break loudly. It is the key that walked out of a repository, the busy afternoon that becomes a bill, and the confident answer that was wrong — so those are the three we built around.
A dial rather than a switch, and one we turn on your behalf. Most work never needs the far end of it, which is rather the point.
Ready for launch / access by arrangement