Skip to main content

What is the Wreken Spec?

Table of Contents​

One-line Definition​

Wrekenfile is a language-agnostic, semantic specification for describing SDKs and APIs so that LLMs can reliably understand, reason about, and compose them into workflows.

Wrekenfile is a semantic IR that turns SDKs and APIs into LLM-readable building blocks for correct workflow generation.

What Wrekenfile Describes​

Wrekenfile models what a callable does, not how it is implemented.

It captures:

  • Constructors - How a client or resource is created
  • Methods / Operations - What actions can be performed
  • Inputs - Parameters, required vs optional fields, defaults, structured inputs
  • Execution Semantics - Sync vs async, streaming vs non-streaming
  • Outputs - Return values and structured data
  • Errors - Failure cases and error types
  • Auth & Preconditions - What must exist or be satisfied before a call
  • Workflows - How calls chain together meaningfully

It works consistently across:

  • REST APIs
  • Frontend SDKs
  • Backend SDKs
  • Go, TypeScript, Python, Java, Rust, C#, Kotlin, PHP

What Wrekenfile Does Not Do (By Design)​

Wrekenfile intentionally does not model:

  • Programming language syntax
  • Runtime behavior (retries, timeouts, caching)
  • UI rendering or frontend frameworks
  • Transport configuration details
  • Auth internals or token storage
  • Business rules or domain validation
  • Performance tuning
  • Version migration logic

These exclusions keep the spec small, stable, and hallucination-resistant.

Why Wrekenfile Exists​

Traditional specs (OpenAPI, SDK docs, READMEs):

  • Are optimized for humans, not LLMs
  • Mix syntax, runtime details, and semantics
  • Become too large and noisy for model reasoning

Wrekenfile solves this by:

  • Normalizing SDKs and APIs into pure semantics
  • Making specs chunkable without losing context
  • Reducing token usage
  • Preventing hallucinations
  • Enabling deterministic workflow generation

Core Design Principle​

If it affects how code runs or renders, it's out of scope. If it defines what a callable does and returns, it belongs in Wrekenfile.

How it works?​

Wreken flow

What is supported?​

The Wreken spec supports the most widely used API and SDK specification formats, allowing seamless generation of Wrekenfiles that make methods, endpoints, inputs, and outputs easily understandable for both developers and LLMs.

The Wreken spec supports multiple API and SDK formats for seamless integration into existing development workflows.

Next Steps​