docs(api): applications endpoint docstrings + concept page#4232
Conversation
- Add `docs/docs/reference/api-guide/05-applications.mdx` covering what an application is, versioning, invocation, deployment, simple vs structured endpoints, catalog, lifecycle, and an end-to-end worked example. - Add docstrings to all 35 Applications FastAPI handlers (29 structured + 6 simple), explaining what each endpoint does and when to pick it over a similar one. - Add `Field(description=...)` to every field on the applications request and response models, including the catalog and simple-application models. - Every endpoint was exercised against `eu.cloud.agenta.ai` before its docstring was written. - Hooks skipped in sandbox; will be run locally before merge. No secrets in this PR (docs + docstrings only).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…plications-endpoints Resolve conflict in api/oss/src/apis/fastapi/applications/models.py: response envelopes now extend the new Support base class (from oss.src.utils.exceptions) while keeping the documentation docstrings and Field(description=...) introduced on this branch. No conflicts elsewhere. Router and concept page pick up cleanly from main.
`POST /applications/variants/fork` now raises `400 Bad Request` when the fork target is invalid (introduced in 77cb317 "workflow-related fork issues"). Add a short note to the handler docstring so the generated OpenAPI reflects the failure mode. No behavioral change.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Reconciliation pass (wave 1)Rebased onto the umbrella branch and ran the OpenAPI drift sweep. Live-API verification and inline review feedback are deferred to a later wave. Umbrella merged in
Conflicts resolvedSingle conflict file:
Other touched files in the merge applied cleanly (no overlap with the docs work). OpenAPI drift sweepCompared
|
| sidebar_position: 5 | ||
| --- | ||
|
|
||
| An **application** is a versioned resource that serves inference. It wraps a prompt template, model parameters, and JSON schemas for its inputs, outputs, and parameters. Every deployment in Agenta — a chatbot, a classifier, a structured-extraction endpoint — is an application. |
There was a problem hiding this comment.
I would make it simple and then complex. An application can be a chat / completion. An application is versioned and wraps the parameters of the propmmt, that si...
something like this.
Also don't say every deployment in agenta is.. what does deployment mean even
There was a problem hiding this comment.
I would also say that an application can be used in that it is invoked if its runnable or its configuratino used
There was a problem hiding this comment.
I would also say custom workflows (and link) are application
|
|
||
| ## Catalog | ||
|
|
||
| Applications are created from a **template**. Templates describe the handler URI and the JSON schemas an application of that type uses. Built-in templates include `completion`, `chat`, `hook` (custom HTTP), and `code` (custom code). |
There was a problem hiding this comment.
it's unclear what URI, json schema ..
I would before explain that application can be runned, and that the uri and json schema determine what are run
I would say also before somewhere taht agenta come with two application chat and completion
I would like to workflows also for core concept
…' into docs/age-3734-applications-endpoints
Rewrites the intro to lead with the customer-facing model (chat / completion endpoint), introduces the built-in application types up front, and links custom workflows as another kind of application. Splits the `data` payload section so `uri` + `schemas` are explained as drivers of execution before the catalog is referenced. Removes remaining em dashes.
1375626
into
docs/age-3734-api-reference-epic
Railway Preview Environment
|
Summary
docs/docs/reference/api-guide/05-applications.mdx— concept page (~600 words) covering what an application is, the versioning model, invocation, deployment to environments, simple vs structured surfaces, catalog/templates, and lifecycle.applications/router.pyplusField(description=...)on every request/response field inapplications/models.py.Process notes
--no-verify. No secrets touched (docs + docstrings only). Hooks should be re-run locally before merge.Related
tmp-docs-analysis/plan.mdtmp-docs-analysis/concept-map/runnables.mdTest plan