go-latitude-llm

Unofficial Go client for the Latitude LLM ops platform API at latitude.so (not Latitude.sh), generated with oapi-codegen. Package latitude (github.com/psyb0t/go-latitude-llm) provides latitude.NewClientWithResponses with a typed ...WithResponse method for every endpoint: projects, traces and spans, scores and annotations, saved searches, issues, API keys, OAuth keys, account and members. Auth is an organization API key or user OAuth token as a Bearer header added through a request editor. Use when Go code needs to call the Latitude LLM API, or already imports go-latitude-llm.

Unofficial, typed Go client for the Latitude LLM ops platform at latitude.so. The package is latitude at the module root. This is not a client for Latitude.sh.

Read references/setup.md before writing calls. It covers installation, auth, the compiled usage example, methods, pagination and response handling.

Security & safety

• Read an organization API key from LATITUDE_API_KEY. Use WithRequestEditorFn to set Authorization: Bearer <key>. Never hardcode, print or log credentials or request headers.
• Use https://api.latitude.so as the base URL. Generated paths already contain /v1. Set a custom HTTP timeout through WithHTTPClient when needed.
• The operation descriptions require user OAuth tokens for CreateSavedSearch, InviteMember, UpdateMember and RemoveMember, despite their ApiKeyAuth security declarations. Token acquisition is outside this client. API-key account responses have null user and role fields.
• Creating scores, annotations, searches and projects, changing issues, revoking keys, inviting members and deleting resources affect the organization. Perform those actions only within the user's request. Exports can send data by email.
• Keep trace contents and member information out of logs. Only send credentials to the user's trusted API URL.

When to use

• Go code needs to inspect Latitude projects, traces, spans, scores or issues.
• Go code needs an authorized write or organization-management operation.
• The project imports github.com/psyb0t/go-latitude-llm.

When not to use

• The code is not Go, or the service is Latitude.sh.
• The user needs a client maintained by Latitude. This package is unofficial.
• The task changes the generated client itself. Follow the repository's AGENTS.md instead.

Finding endpoints and types

The reference covers a few calls. Every operation in the spec has a generated method, and the spec's descriptions are on them as Go doc comments. Look names and fields up instead of guessing. After go get github.com/psyb0t/go-latitude-llm, from inside your module:

bash

go doc github.com/psyb0t/go-latitude-llm ClientWithResponsesInterface  # every endpoint method
go doc github.com/psyb0t/go-latitude-llm CreateProjectBody             # one method, params type or model
go doc -all github.com/psyb0t/go-latitude-llm                          # the whole package

The same documentation is at https://pkg.go.dev/github.com/psyb0t/go-latitude-llm.

Method names come from the spec's operation IDs. <OperationId>WithResponse takes the context, then the path parameters in order, then *<OperationId>Params when the operation has query or header parameters, then the request body when it has one. The JSON200 field (or JSON201 and so on, per declared status) holds the decoded body; it is nil for any other status.

Working with the client

Use NewClientWithResponses and the operation's ...WithResponse method. Check the Go error, HTTP status and expected success field before reading the result. JSON200 and JSON201 are pointers; non-success statuses do not automatically produce Go errors. Nullable model fields are pointers too.

Method names come from the spec's operation IDs. Scores use float64, and union schemas expose generated From... and As... helpers. Inspect the generated signature before constructing a union request. ListProjects takes no params, and the spec says the project list fits in a single page. Other collections carry operation-specific cursor fields.

Finish by compiling the calling code and testing its requests against a local HTTP server. Do not call the live API merely to validate an example.