What you can do with AgenticOrg
AgenticOrg is a workspace for building and operating AI agents around your procedures, documents and approved business tools. It brings agents, knowledge, workflows, approvals and run evidence together. You decide the task and the boundaries; an agent is not a replacement for your organization's authority to make a financial, legal or customer decision.
You can start with a document question, then progress to a repeatable workflow. You do not need to connect every system before the first useful task. A model and a small, approved knowledge set are enough for a read-only learning exercise.
- 1Choose a task
Pick one narrow job with a clear owner and a measurable outcome.
- 2Add knowledge and tools
Supply current procedures and only the permissions required.
- 3Test with sample data
Inspect evidence, errors and refusals before relying on outputs.
- 4Run under review
Assign operators, approvals, support and change control.
Choose your learning path
| Your role | Start with | Then learn |
|---|---|---|
| First-time user | Your first useful agent | Knowledge and OCR, Run and chat |
| Administrator | Workspace and roles | Model setup, Model Gateway, Guardrails, Connectors |
| Process owner | Create agents | Workflows, Approvals, Evaluation |
| Bank or fintech team | Business onboarding | Reconciliation, Customer service |
| Merchant team | Commerce | BFSI merchant services |
| Developer or IT team | API, SDK, MCP and A2A | Self-hosting |
Before you begin
- Obtain an account at app.agenticorg.ai or your organization's reviewed deployment. Accept an invitation if your organization already exists; do not create a second organization simply to join your team.
- Ask the administrator which company and role you should use. Company selection matters for business data and connector access.
- Confirm that a model provider is configured for your task. Your login does not automatically provide every external provider credential.
- Use synthetic or approved non-sensitive material for your first exercise. Do not upload customer identity documents as a trial.
- Know who can approve outputs and who owns the connected system.
What availability means
For regulated workflows, first read the BFSI capability status. The five process maps are fictional configured examples; 15 of 150 assessed functional capabilities are covered, 102 are partial and 33 remain gaps.
Implemented means a runtime path exists. Configuration-dependent means it also needs credentials, permissions, worker infrastructure or tenant settings. Example means a teaching scenario, not a pre-integrated solution. A listed connector, agent template, voice provider or channel is not proof of successful live execution in your workspace.
Shopify read-only commerce sync and the signed Twilio voice runtime have specific implemented paths. Other commerce sources and voice-provider options do not automatically have equivalent runtime support. OACP buyer answers and prepared handoffs do not themselves create orders or collect money. Jev advisory integration is access-gated and is not an active production decision authority.
Find the right screen
These links open the hosted application. Sign in first and select the correct company. On a self-managed deployment, use its hostname with the same path. Some screens are restricted by role; a missing menu is not an invitation to bypass permissions.
| I want to... | Screen | Read first |
|---|---|---|
| Choose a company | Companies | Workspace and roles |
| Connect a model | AI Provider Credentials | Model setup |
| Find or create an agent | Agents | Create agents |
| Build from a procedure | Create from SOP | Create agents |
| Upload a document | Knowledge Base | Knowledge and OCR |
| Connect a business service | Connectors | Connectors |
| Coordinate several steps | Workflows | Workflows |
| Review proposed actions | Approvals | Human review |
| Review business onboarding | Governed cases | Governed cases |
| Configure voice | Voice Setup | Voice |
| Configure browser automation | RPA | RPA |
| Investigate run evidence | Audit | Monitoring |
| Inspect run timelines | Observability | Run observability |
| Configure model routing | Model Gateway | Model Gateway |
| Configure guardrail rules | Guardrails | Guardrails |
| Configure merchant commerce | Commerce Runtime | Commerce |
| Connect an external agent client | A2A / MCP | API and clients |
| Create an API key | Settings | API and clients |
| Review subscription or usage | Billing | Billing and support |
When you get stuck
Use Troubleshooting to isolate the issue. Record the screen, time, selected company, action and safe error code. Never send passwords, API keys or raw customer files in a support ticket.
The guides describe source-verified behavior, not a promise that your deployment has every optional feature enabled. Ask your administrator about the deployed version and tenant configuration.