Give an AI agent a controlled way to find documents, inspect their metadata, and prepare work for a person to review. FormKiQ supplies the document APIs, site permissions, and AWS deployment boundary; your application defines which tasks the agent can perform.
Use the FormKiQ MCP server for supported document operations, or the separately selected KnowledgeBase module for questions grounded in a document collection. These capabilities can support the same business process through distinct interfaces.
See a supplier-review exampleChoose the connection around the task
| Task | FormKiQ capability | Scope to confirm |
|---|---|---|
| Find a file, inspect attributes, or check processing state | MCP server over supported FormKiQ APIs | Exposed tools, the caller's JWT permissions, site access, and client/model handling of results. |
| Ask a question across an approved collection | KnowledgeBase, powered by Amazon Bedrock | Collection ingestion, access enforcement before generation, source references, and index freshness. |
| Extract fields or classify an incoming document | AI Processing and Analysis | Models, prompts, mappings, validation, and review rules for the document type. |
The MCP server exposes a selected API surface. It does not turn every FormKiQ feature into a tool or install KnowledgeBase. KnowledgeBase and AI Processing and Analysis are separate Advanced and Enterprise add-ons.
Illustrative workflow · fictional supplier
Prepare a supplier renewal review
A procurement specialist asks an assistant to find Sample Orchard's current agreement and identify the evidence needed for renewal. The Vendor and Supplier Document Management solution provides the application for supplier documentation and review; the assistant helps staff navigate that work.
- 1 · Locate
Find the relevant records
Use authorized metadata searches and document reads through MCP to locate the supplier's agreement and supporting records in the permitted site.
- 2 · Prepare
Ground the response
Read the permitted evidence, or query an approved KnowledgeBase collection. Include document references and identify missing evidence for the reviewer.
- 3 · Review
Keep the decision accountable
The specialist verifies the source and makes the renewal decision in the configured workflow. Any agent write operation needs its own authorization and review policy.
The supplier mappings, interface, agent instructions, and review rules are configuration and integration choices for this workflow. This example describes a scoped integration rather than a preinstalled autonomous renewal agent.
Keep the processing boundary explicit
A customer-managed FormKiQ deployment stores its primary documents and metadata in your AWS account. An MCP client can send returned content to its own model provider. Deploying FormKiQ in your account does not determine where that client processes data.
KnowledgeBase and AI Processing and Analysis use Bedrock through the configured AWS account. The selected model, inference profile, retrieval services, logs, and integrations determine the wider processing boundary. AWS distinguishes geographic and global inference profiles; approve the actual configuration against your residency requirements.
Evaluation checklist
- Choose one task and representative documents; define what a useful result looks like.
- Use a dedicated identity with the required site and document permissions. Start with read-only MCP tools.
- Test unauthorized access and permission revocation as well as successful retrieval.
- For indexed retrieval, verify entitlements before generation and reconcile changed or deleted sources.
- Review model destinations, retained prompts, logs, and cached responses.
- Treat document contents as untrusted input; define human review and permitted mutations explicitly.
Start with a document task you can verify
FormKiQ fits agents that need document operations alongside API integration, tenant separation, and deployment control. Connect the smallest useful tool set, validate access and evidence, then expand the workflow based on observed results.
Inspect the MCP implementation · Inspect API access controls · Embed document management in your product
Scope an agent-assisted document workflow
Bring one task, the intended users, and the document and model boundaries. We can identify the appropriate application, API connection, and selected modules for an evaluation.
Book a workflow review