master-zapier-plan-draft/packages/verae-access-api
George Lambert 1b199ca4d4
Some checks are pending
offline / test (push) Waiting to run
Separate Zapier, web, API, and leaf access planes with NATS authz
Zapier is one ingress. Direct web, customer API, and S2S leaf nodes are their own services. Every hop to an internal subject must pass verae.access.authz.check (default deny by plane).
2026-09-11 16:05:05 -04:00
..
src Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
test Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
NATS.md Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
package.json Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
README.md Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00

verae-access-api

Direct customer API plane (x-api-key). Separate from the Zapier Platform app.

Forgejo: https://git.georgelambert.org/marchon/verae-access-api

Address path: verae.access.api.*verae.access.authz.checkverae.billing.statement.get / verae.zapier.jobs.watch (HTTPS to middleware, not a Zapier NATS client).

Cannot balance.adjust or archive.put.

Port :3022.