Integration TestingReads data
Mock Provider Echo
Local executable action for validating StackOS auth, grants, redaction, audit, and failure handling without provider accounts.
Utilities plugin
Mock Provider
Local fake provider for end-to-end StackOS action execution tests without external API accounts.
Connection facts
What the Mock Provider connector actually exposes.
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
- Connection method
- api-key
- Setup
- No vendor registration exists. Use any non-empty fake key when testing StackOS credential and action execution flow.
- Capability groups
- Integration Testing
- Action boundaries
- 1 read action
Action catalog
Actions listed for Mock Provider.
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
1 matching action
Direct answer
How does the Mock Provider integration work?
People continue using Mock Provider as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
- 01Your requestStart in your AI
- 02StackOS planExpands the steps
- 03Mock ProviderDoes its bounded part
- 04Checked resultKeeps the proof
More from Utilities
Related integrations.
Utilities
Alibaba Wan
Alibaba Model Studio Wan async video generation provider.
Video Generation
Utilities
Amazon S3
Amazon S3 general-purpose bucket and optional path connection for bounded object listing, transfer, marker, delete, and exact-object move operations.
File Transfer
Utilities
BytePlus ModelArk
BytePlus ModelArk media generation provider.
Image GenerationVideo Generation
Common questions
Mock Provider and StackOS.
What can the Mock Provider integration do in StackOS?
The current catalog includes 1 Mock Provider action across Integration Testing. The exact actions used depend on the workflow and approval rules.
Does StackOS replace Mock Provider?
No. Mock Provider remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.