Signatures

Signatures are the contract between your application and the model. They name the inputs, name the outputs, define field types, attach field descriptions, and give Ax enough structure to generate prompts, parse results, validate values, retry failures, expose tools, trace usage, and optimize examples.

from axllm import s

sig = s('email:string -> priority:class "high, normal, low"')

flowchart LR
  A[Signature string or builder] --> B[Prompt contract]
  A --> C[JSON schema]
  A --> D[Parser]
  D --> E[Validation]
  E -->|valid| F[Typed output]
  E -->|invalid| G[Correction feedback]
  G --> B

Grammar

The compact form is:

inputField:type, optionalField?:type -> outputField:type, listField:type[]

Everything before -> is input. Everything after -> is output. Field descriptions can be attached as quoted text, and narrow class fields make enum-style output explicit.

Types accept an optional modifier bag in parentheses, and objects can declare structured fields inline — the string form expresses everything the fluent API can (except Standard Schema fields):

userAge:number(min 0, max 120),
contactEmail:string(format email, cache),
codeSnippet:code(python)
->
userName:string(pattern "^[a-z_]+$" "lowercase name"),
tagList:string(item "a short tag")[] "all tags",
profileList:object{ fullName:string, userAge?:number(min 0) }[] "matched profiles"

Modifiers that don’t apply to a type are hard errors — the string API is the strict surface, whereas the fluent API silently ignores a .min() on a boolean.

from axllm import s

sig = s("question:string -> answer:string")
schema = sig.to_json_schema("outputs")

Field Types

Modifier bag entries (comma-separated, order-free):

Good signatures use domain names: customerEmail, policyQuestion, riskScore. Avoid input, data, output, and other names that force the model to infer intent from prose.

Fluent API

The fluent builder is the best option when a signature needs constraints, descriptions, cache hints, internal fields, or programmatic composition. In TypeScript this is the f() builder. Generated language packages expose the AxIR-supported signature surface available in that package.

from axllm import s

sig = s("question:string -> answer:string")
schema = sig.to_json_schema("outputs")

Chainable field modifiers are deliberately simple:

Validation And Retries

A signature is not just documentation. Ax validates parsed field values and can retry with correction feedback when the model returns malformed JSON, an invalid class value, a bad email, a reversed date range, or a value that violates schema constraints.

from axllm import s

sig = s("question:string -> answer:string")
schema = sig.to_json_schema("outputs")

Validation happens after parsing complete fields. For streaming generation, streaming assertions can fail fast at field boundaries and feed correction feedback into the next attempt.

Standard Schema

Standard Schema support is a TypeScript surface today. Use it when you want zod, valibot, or arktype constraints to sit beside the Ax signature and feed the validation/retry loop.

Generated language packages expose the AxIR-supported signature and JSON-schema surfaces for their native package. They preserve the same contract idea, but they do not pretend that TypeScript schema libraries exist in the target language.

Media, Cache, And Internal Fields

Media fields let a program receive images, audio, or files when the provider supports them. In agent flows, audio inputs are usually transcribed before planner/executor/responder stages; direct ax(...) programs can pass native media to compatible providers.

Cache hints mark stable context so provider prefix caching can reuse expensive prompt regions. Internal fields let a program ask the model to produce private scratch structure without exposing it in the final typed output.

Reuse And Composition

Start with a string signature, then graduate to parsed or fluent signatures when you need reuse.

from axllm import s

sig = s("question:string -> answer:string")
schema = sig.to_json_schema("outputs")

Signatures As Flow Diagrams

Because the string grammar is text-complete, a whole workflow of signatures can live in one mermaid flowchart — each node’s contract travels in a %%ax comment directive:

flowchart TD
  %%ax summarize: documentText:string -> summaryText:string(max 500)
  %%ax format: summaryText:string -> finalReport:string
  summarize --> format

In TypeScript, passing the diagram to flow() compiles it into a runnable flow, and String(flow) renders any flow back — so the diagram and the program stay in sync.

Signature Gallery

Real-world contracts, one line each — every entry parses as written:

# Support triage: several class outputs plus a capped reply draft
ticketText:string -> priorityClass:class "p0, p1, p2", sentimentClass:class "angry, neutral, happy", replyDraft:string(max 500)

# Invoice extraction: regex-validated id, bounded totals, structured line items
invoiceText:string -> invoiceNumber:string(pattern "^INV-\\d+$" "INV- then digits"), totalAmount:number(min 0), lineItems:object{ description:string, quantity:number(min 1), unitPrice:number }[]

# RAG: cached corpus input plus per-item described citations
corpusText:string(cache), userQuestion:string -> answerText:string, citedChunks:string(item "verbatim quote")[]

# Resume parsing: nested objects inside nested arrays
resumeText:string -> candidateProfile:object{ fullName:string, yearsExperience:number(min 0), skillList:string[], education:object{ schoolName:string, degreeName?:string }[] }

# Code generation: language-tagged code outputs
taskBrief:string -> pythonScript:code(python), testCases:code(python), riskNotes?:string

# Lead scoring: signature-level description, bounded score, class next step
"Score sales leads" leadNotes:string -> fitScore:number(min 0, max 100) "0-100 fit", nextStep:class "call, email, drop"

Production Notes

• Keep fields small and typed. Split unrelated jobs into separate signatures or a flow.
• Use class or schema validation for narrow domains instead of prose-only instructions.
• Put stable context in cacheable inputs rather than repeating it in every field description.
• Use internal outputs for model scratch fields that should not become API response data.
• Treat generated JSON schema as a public contract when tools, SDKs, or external callers rely on it.

See Tools, s() signatures, and s() API.