← Files Runpod (Official)ARCHIVED FILE
skills/flash/evals/connect-existing-endpoint.eval.md
932 Bytes · Oct 4, 2026 · 12:18 UTC
# Call an existing Runpod endpoint by ID
## Prompt
I already have a Runpod serverless endpoint with ID `abc123xyz`. Using
runpod-flash, send it a synchronous job `{"prompt": "hello"}` and print the
output. The first request may cold-start and take longer than a minute.
## Expected behavior
The agent should:
1. Create `Endpoint(id="abc123xyz")` — connects to the existing endpoint, no provisioning
2. Submit the job with `runsync`, raising the timeout above the 60s default to survive cold start
3. Print `job.output`
## Assertions
- Creates `Endpoint(id="abc123xyz")` (no `name=`, `gpu=`, or `image=` needed)
- Uses `await ep.runsync({"prompt": "hello"}, timeout=...)` with a timeout > 60 (e.g. 120) OR uses `await ep.run(...)` + `await job.wait()` to avoid the 60s cap
- Accesses the result via `job.output`
- Uses `await` on the call
- Does NOT pass `id=` together with `image=` (`id=` + `name=` is legal and harmless)
SHA-256: 88514281b4da83758f8b634bb152f8b2efb5831877af7b0f86f3eefbf1229cc0