new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

AI SDK · Providers · all subjects

maxim/options

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Maxim custom metadata fields for entity naming

Maxim supports the following entity naming metadata fields: sessionName (override default session name), traceName (override default trace name), spanName (override default span name), and generationName (override default LLM generation name).

Maxim custom metadata fields for entity tagging

Maxim supports the following entity tagging metadata fields: sessionTags (object with key-value pairs to add to session), traceTags (object with key-value pairs to add to trace), spanTags (object with key-value pairs to add to span), and generationTags (object with key-value pairs to add to LLM generations).

Maxim custom metadata fields for ID references

Maxim supports the following ID reference metadata fields: sessionId (link trace to an existing session), traceId (use a specific trace ID), and spanId (use a specific span ID).

Maxim metadata usage in generateText

Custom Maxim metadata is passed via the providerOptions.maxim field when calling generateText. The metadata object should be typed as MaximVercelProviderMetadata. Example: providerOptions: { maxim: { traceName: 'custom-trace-name', traceTags: { type: 'demo', priority: 'high' } } as MaximVercelProviderMetadata }

Give your agent this brain