You're already set up if you've signed up and swapped your base URL — everything past that point is verification and getting oriented in the dashboard. Here's the full path, in order, so nothing feels like guesswork on your first pass through.
1. Three steps: sign up, swap your base URL, send a test request. No SDK install, no code restructuring.
2. Your first request shows up in the dashboard within about a minute of going through.
3. Your first recommendation is typically ready within 24 hours, once there's enough traffic to spot a pattern.
The Three Setup Steps
Create your account
Email and password — no credit card required to start. You land in the setup flow immediately after signing up, where you'll get your unique proxy URL.
Swap your base URL
This is the entire integration. Wherever your code currently points at your provider's API directly, point it at Preto's proxy URL instead — everything else about your existing SDK usage stays the same.
# Before
client = OpenAI(api_key="sk-...")
# After — same SDK, same code, different base URL
client = OpenAI(
api_key="sk-...",
base_url="https://proxy.preto.ai/v1/YOUR-KEY"
)
Your actual provider API key stays exactly where it already lives — Preto forwards the request on, it doesn't replace your credentials.
Send a test request and verify
Trigger one real call through your app — a normal chat completion, a classification call, whatever your app already does. If your app responds normally, the integration is working; Preto is transparent to your application code, so there's no different response shape to handle.
What Happens in the First 24 Hours
Already connected?
Here's what to look at first once your data starts flowing in.
Open Your DashboardYou're already set up. Here's what to look at first.
The Recommended Path: Staging Before Production
Even though the integration is a single line, it's still worth deploying it to staging first, confirming normal app behavior, and then rolling to production — the same discipline you'd apply to any config change touching a critical path. Preto forwards every request exactly as sent and returns the provider's response unchanged, but verifying that in a lower-risk environment first costs a few minutes and removes any doubt before it matters.
Once you're confident it's working, the next step is learning to read what the dashboard is actually telling you — that's covered in the 5-minute dashboard guide. And once you've got a few days of real traffic flowing through, these are the five things worth doing in your first week to get the most out of it quickly.
Frequently Asked Questions
How long does it take to set up Preto?
Do I need to install an SDK to use Preto?
How long until I get my first cost-saving recommendation?
Will connecting Preto break my existing app?
Your setup is done. Here's where to go next.
Open your dashboard to see your first cost data, or jump straight to the guide on what each number means.
Open Your DashboardQuestions about setup? Reply to your welcome email — we read every one.