Bedrock operations
Every Bedrock operation Overcast declares — 2 of 2 implemented — with status, behaviour notes and a link to the AWS API reference for each.
All 2 listed operations are implemented. Back to Bedrock.
Summary
| Category | 🧊 Inert |
|---|---|
| Inference | 2 |
Endpoints
Inference
| Operation | Status | Notes | AWS Docs |
|---|---|---|---|
InvokeModel | 🧊 Inert | POST /model/{modelId}/invoke — accepted and answered 200; the required payload is not parsed and no model runs. The response body is an opaque blob whose format belongs to the model, which Overcast does not emulate, so it returns one self-describing field rather than any model family’s shape | docs |
Converse | 🧊 Inert | POST /model/{modelId}/converse — accepted and answered with a complete ConverseResponse, every @required member present; no inference runs, so the assistant text is canned and the token counts and latency are zero | docs |
Related
- Bedrock — quick start, what works, and the differences from AWS
- All service pages