Platform
Prana IQ runs tenant-fenced agents with your knowledge and your tools. You define skills, connect toolsets (including MCP), and keep a human in the loop before anything writes back.
Instruction plus knowledge plus tools is your agent. Every request stays inside one customer account.
Agents
Instruction + Knowledge + Tools = Your Agent. You configure tenant-fenced agents for concrete ops work. They stay inside your customer account.
What this covers
- Plain-language instructions
- Customer-scoped knowledge
- Connected tools you assign
How you reach them
- Web portal
- Connect with an API key
- Connect with MCP
Skills
A skill is the instruction set and toolset an agent runs with. You define them, assign tools, and reuse them across agents in your account.
What this covers
- Instructions you write
- Toolset assignment per agent
- Reusable across agents
Why it matters
- You define what the agent can do
- No hidden default behavior
- Changes are yours to make
Tools and MCP
Agents call built-in toolsets or tools connected through OAuth, or toolsets you register yourself. You can also connect MCP servers as toolsets. Availability is set explicitly per customer.
What this covers
- Built-in toolsets
- OAuth connections such as Google Drive, Gmail, and Notion
- Customer-registered toolsets
- MCP servers as toolsets
Why it matters
- Credentials stay scoped to your account
- Tool availability does not cross accounts
- You choose what each agent can call
Knowledge
Customer-scoped knowledge the agent searches on demand, not a static file dump. Documents are chunked and indexed inside one tenant boundary.
What this covers
- Documents and knowledge sources
- Chunked and indexed for search
- Scoped to your customer account
- Retrieved on demand
Why it matters
- Answers are grounded in your material
- Knowledge does not cross accounts
- No automatic dump of every document
Approvals
Tools flagged for approval pause for a human before they run. You can approve a session guard so similar calls are auto-approved for the rest of that session.
What this covers
- Approval gates on flagged tools
- Session guards for repeat approvals
- Usage and tool-call records
Why it matters
- Humans stay in the loop where it matters
- Activity is reviewable after the fact
Chat, API, and MCP
Talk to agents in the web portal. Connect with an API key. Connect with MCP. Every request resolves to one customer account.
What this covers
- Web portal
- Connect with an API key
- Connect with MCP
Why it matters
- Use the portal or call agents from your own tools
- The same tenant fence applies on every path
Ready to run it?
Book a call. We will walk through your operations and the hosted platform.
Book a call