The endpoint catalog, grouped by capability.

# Auth is a platform-standard SS-01 OIDC token + your tenant header.
export BASE="https://api.edge.nexocloud.io/api/v1"
export AUTH="Authorization: Bearer $TOKEN"     # from signup / SS-05 key
export TENANT="X-Tenant-Id: acme"

# Create a bucket, deploy a function, route it, roll out.
curl -X POST "$BASE/buckets" -H "$AUTH" -H "$TENANT" \
  -H "Idempotency-Key: $(uuidgen)" -d '{"name":"site-assets","versioning":true}'

curl -X POST "$BASE/functions" -H "$AUTH" -H "$TENANT" -d '{"name":"assets-router"}'
curl -X POST "$BASE/functions/assets-router/deploy" -H "$AUTH" -H "$TENANT" \
  -d '{"code":"export default { fetch(req, env){} }","promote":true}'
curl -X POST "$BASE/functions/assets-router/rollout" -H "$AUTH" -H "$TENANT"

# The /s3 wire gateway speaks S3 REST with AWS Signature V4.
# Point any real S3 client at it — tenant is resolved from the access key.

# 1. Issue an S3 access key (secret shown ONCE)
curl -X POST "$BASE/object/access-keys" -H "$AUTH" -H "$TENANT" \
  -d '{"name":"ci-deploy"}'
#  → { "access_key_id": "EDGE...", "secret_access_key": "***shown once***" }

# 2. Configure the AWS CLI against the wire gateway
aws configure set aws_access_key_id     EDGE...
aws configure set aws_secret_access_key  ***
export S3="https://api.edge.nexocloud.io/s3"

# 3. Use it like S3 — ListBuckets, PutObject, multipart, all SigV4-signed
aws --endpoint-url "$S3" s3 ls
aws --endpoint-url "$S3" s3 cp app.v42.js s3://site-assets/app.v42.js
# boto3 / any S3 SDK works the same way.