# API context for AGENTO

## Goal and scope
- What user operation should the integration support?
- Which single operation will be connected first?

## Sources and version
- Documentation file or URL:
- operationId or route:
- Contract review date:

## First endpoint
- Method: UNKNOWN
- Complete URL: UNKNOWN
- Does this operation change data? UNKNOWN

## Request fields and value ownership
For each field record its API name, type, path/query/body location, requiredness, value owner, and documented constraints. Never put credential values here.

## Authentication and trusted context
- Authentication scheme:
- Environment variable name, if applicable:
- Values supplied by the backend after authentication:

## Request and response examples
Use sanitized examples from your API. Distinguish a sample response from a contract guaranteeing required fields.

## Known errors
Status, meaning, and appropriate application response.

## Dependencies and choices
Which endpoint supplies identifiers? What is the list path, item ID, and display label?

## Writes and confirmation
What changes? What must the user review? Does the API support idempotency? Mark unsupported assumptions UNKNOWN.

## Unknowns and assumptions
Resolve these before generating executable configuration.

## Expected acceptance test
A known successful request, its inputs and expected result, and one missing-input case.