Every client is generated from the same OpenAPI document, so field names, error types, and streaming events line up across languages. Retries, backoff, and timeouts are built in.
Sync and async clients, typed with Pydantic models.
pip install vantafoldfrom vantafold import Vantafold
client = Vantafold()
r = client.reason(model="auto", input="Ping.")
print(r.output_text)TypeScript-first, works in Node and any edge runtime with fetch.
npm install @vantafold/sdkimport { Vantafold } from "@vantafold/sdk";
const client = new Vantafold();
const r = await client.reason({ model: "auto", input: "Ping." });
console.log(r.output_text);Context-aware, zero third-party dependencies.
go get github.com/vantafold/vantafold-goclient := vantafold.New()
r, err := client.Reason(ctx, vantafold.ReasonRequest{
Model: "auto",
Input: "Ping.",
})
fmt.Println(r.OutputText)Idiomatic Ruby with keyword arguments and lazy streaming enumerators.
gem install vantafoldrequire "vantafold"
client = Vantafold::Client.new
r = client.reason(model: "auto", input: "Ping.")
puts r.output_textBuilder-style requests, JDK 17+, works with virtual threads.
implementation("ai.vantafold:sdk:3.4.0")var client = new VantafoldClient();
var r = client.reason(ReasonRequest.builder()
.model("auto")
.input("Ping.")
.build());
System.out.println(r.outputText());Async on Tokio, with typed streaming events.
cargo add vantafoldlet client = Vantafold::from_env()?;
let r = client
.reason(ReasonRequest::new("auto", "Ping."))
.await?;
println!("{}", r.output_text);Idempotent failures retry three times by default with exponential backoff and jitter. Configure or disable it per client.
Requests, responses, streaming events, and errors are typed — Pydantic, TypeScript, Go structs, Sorbet, records, and serde.
Iterators, async iterators, channels, and enumerators — whichever is idiomatic — over the same event stream.
VANTAFOLD_API_KEY, VANTAFOLD_BASE_URL, and VANTAFOLD_PROJECT are read automatically.
Test keys return deterministic fixtures so CI never bills you and never flakes on a provider outage.
A single binary runs the router locally, so integration tests exercise real routing logic offline.
| Language | Package | Maintainer | Status |
|---|---|---|---|
| PHP | vantafold/vantafold-php | Community | Actively maintained |
| Elixir | vantafold_ex | Community | Actively maintained |
| .NET | Vantafold.Sdk | Community | Actively maintained |
| Swift | VantafoldKit | Community | Beta |
| Clojure | vantafold-clj | Community | Beta |
Community clients are not covered by the Vantafold SLA. If you maintain one, tell us and we will list it here.
Two minutes from empty file to first response.