Skip to content

Generate a production config you can copy

Pick authentication, region, client and limits. Copy a config and client snippet that run, with the latency they imply. Runs in your browser. No account, no card, no call.

Your service

Generates locally. Copy the output and it runs.

p50 latency
25 ms
p99 latency
80 ms
Worst case
30.3 s
all retries exhausted
my-service.config.yaml yaml
# my-service — generated by ACPtify
# Copy to my-service.config.yaml. Every value below is live, not a placeholder.
apiVersion: v1
kind: Service
metadata:
  name: my-service
  region: us-east
spec:
  endpoint: https://my-service.acptify.com/v1
  auth:
    mode: apikey
    credential: ${MY_SERVICE_TOKEN}
  limits:
    requestsPerMinute: 600
    timeoutMs: 10000
    maxRetries: 2
    backoff: exponential
  observability:
    structuredLogs: true
    tracing: w3c
    replayRetentionDays: 7
Try it now bash
curl -sS https://my-service.acptify.com/v1/run \
  -H "X-API-Key: $TOKEN" \
  -H "Content-Type: application/json" \
  --max-time 10.0 \
  -d '{"input": {"task": "hello"}}'
Client node
import { Client } from "@my-service/sdk";

const client = new Client({
  endpoint: "https://my-service.acptify.com/v1",
  auth: { mode: "apikey", token: process.env.TOKEN! },
  timeoutMs: 10000,
  maxRetries: 2,
});

const result = await client.run({ task: "hello" });
console.log(result.data);
Things this configuration will do to you
  • API keys do not expire on their own. Set a rotation reminder now.

Take this with you

No email required. It is your result.

ACPtify — config
· my-service · us-east · apikey
· p50 25ms, p99 80ms
· 1,500,000 requests/month at 600 rpm burst

Run it yourself: https://acptify.com

Generate a production config you can copy

Pick authentication, region, client and limits. Copy a config and client snippet that run, with the latency they imply. Runs in your browser. No account, no card, no call.

Open the free tool

It runs in your browser. ACPtify never sees your inputs.