B2B · Agent development & automation
Portly AI LLC supplies an Agent Control Plane. The Agent Library lists Invoice Parser (Finance · Running), Ticket Router (Support · Running), and Inventory Watcher (Operations · Running). The canvas is Retrieve → Reason → Tool Call → Write Back, each marked Completed. The Execution inspector shows Status Succeeded, duration, and JSON output with invoices_processed. Finance, Support, and Operations are workspace tabs in the same shell.
Platform map
Each berth is a licensed module on the same control plane. Buyers start with Agent Studio, add the Automation Framework for Invoice Intake jobs, then lock the estate with the Enterprise Policy Center.
Authors set Agent Name, Model, Tools, Memory, and Guardrails. The Tools pane lists HTTP Request, SQL Query, and Document Search. Model is selected from the Model field. Memory is Conversation Buffer. Guardrails is Content Moderation. A run can therefore fetch over HTTP, query SQL, and search documents under those two controls.
Invoice Intake is a five-card pipeline: Trigger, Classify, Act, Verify, and Log. The Trigger card binds Slack, Email, and ERP. Retry Policy is Max attempts 3 with exponential backoff. SLA Timer target is 30 minutes, escalate after 60 minutes.
Role Permissions cover Operator, Analyst, and Admin against View Runs, Deploy Agents, Edit Tools, and Export Logs. Feature Policies are SSO, Audit Log, and Data Residency set to United States.
Agent development
Invoice Parser, Ticket Router, and Inventory Watcher ship on a standard control-plane license. Each agent is a versioned record: Model, tool allow-list, Conversation Buffer, and Content Moderation stored beside run history.
Finance workspace. Evaluation Harness cases INV-001 through INV-006 score Expected Tool versus Actual Tool (PDF Parser or OCR Engine) in the Pass column.
Support workspace. Classifies a ticket, selects a queue, and records the route on the Retrieve → Reason → Tool Call → Write Back canvas.
Operations workspace. Reasons over stock thresholds, then emits a Tool Call. Admin deploys the version through Development, Staging, and Production.
Intelligent automation
Trigger starts Invoice Intake from Slack, Email, or ERP. Classify labels the payload. Act executes allow-listed tools. Verify checks the write-back. Log stores the timeline. Run Observability prints Time, Step, Tool, Tokens, and Status, including HTTP Request and SQL Query rows with a Succeeded badge.
Slack, Email, or ERP starts Invoice Intake. The SLA Timer starts with the trigger (target 30m).
Classify sits between Trigger and Act so Act never fires on an unlabeled document.
HTTP Request and SQL Query appear as Tool rows with token counts. Retry Policy: max 3, exponential backoff.
Succeeded is recorded only after Verify. Escalate after 60m if the SLA Timer expires.
Enterprise-grade tools
Enterprise buyers get a Connector Registry and a Runtime Deployment board in addition to the Policy Center. Roles remain Operator, Analyst, and Admin.
Six cards ship Connected: Email, Slack, REST API, PostgreSQL, SharePoint, and ServiceNow. HTTP Request and SQL Query in Agent Studio bind to REST API and PostgreSQL. Invoice Intake uses Slack, Email, and ERP on the Trigger card.
Development shows agent version v2.3.1-dev and replica count 3. Staging shows v2.3.1-stage and replica count 6. Production shows v2.3.1 and replica count 12. Each column is Healthy. Admin is the Policy Center role that may Deploy Agents into Production.
How a run moves
This is the canvas contract on the Agent Control Plane. Finance, Support, and Operations share the same four nodes. The Execution inspector records Succeeded only after Write Back completes.
Pull source records through Document Search, Email, SharePoint, or HTTP Request before Reason is allowed.
The Model field in Agent Studio produces the next action against Conversation Buffer and Content Moderation. No write occurs in this node.
Only allow-listed tools fire. Typical Run Observability rows are HTTP Request and SQL Query with token counts.
Verified output lands in ERP, ServiceNow, or PostgreSQL. Succeeded is stored on the Execution inspector when Verify and Log both pass.
Licensing matrix
Use this table in an RFP. Names match the consoles in the figures so legal, security, and engineering review the same vocabulary.
| Module | Primary console | Objects on screen | Who may change it |
|---|---|---|---|
| Agent Control Plane | Fig. 01 | Invoice Parser, Ticket Router, Inventory Watcher; Retrieve, Reason, Tool Call, Write Back; Finance, Support, Operations; Execution Succeeded | Admin deploys; Operator views runs |
| Agent Studio | Fig. 01a | Agent Name, Model, Tools, Memory (Conversation Buffer), Guardrails (Content Moderation); HTTP Request, SQL Query, Document Search | Admin and any role with Edit Tools |
| Automation Framework | Fig. 01b | Trigger, Classify, Act, Verify, Log; Invoice Intake; Slack, Email, ERP; Retry Policy (max 3); SLA Timer (30m / 60m) | Admin; Analyst may view |
| Evaluation Harness | Fig. 02 | Invoice Parser cases INV-001–INV-006; Expected Tool; Actual Tool; Pass; PDF Parser; OCR Engine | Analyst authors cases; Admin promotes |
| Run Observability | Fig. 03 | Time, Step, Tool, Tokens, Status; HTTP Request; SQL Query; Succeeded | Operator with View Runs; Export Logs if granted |
| Connector Registry | Fig. 04 | Email, Slack, REST API, PostgreSQL, SharePoint, ServiceNow — Connected | Admin |
| Runtime Deployment | Fig. 05 | Development v2.3.1-dev / 3 replicas; Staging v2.3.1-stage / 6; Production v2.3.1 / 12; Healthy | Admin with Deploy Agents |
| Enterprise Policy Center | Fig. 01c | Operator, Analyst, Admin; View Runs, Deploy Agents, Edit Tools, Export Logs; SSO; Audit Log; Data Residency United States | Admin only |
Buyer questions
Answers stay inside the product surfaces shown on this page. If a control is not named above, it is not in the current license.
No. The license is a control plane for named enterprise agents, an automation framework, and admin tools. Finance, Support, and Operations work through those consoles.
Invoice Parser, Ticket Router, and Inventory Watcher. Additional agents are authored in Agent Studio with HTTP Request, SQL Query, and Document Search, Conversation Buffer, and Content Moderation.
The Evaluation Harness runs Invoice Parser cases INV-001 through INV-006 against Expected Tool versus Actual Tool (PDF Parser or OCR Engine). Runtime Deployment then promotes a version through Development and Staging. Production shows Healthy only after that path.
Enterprise Policy Center: SSO, Audit Log, and Data Residency United States. Roles are Operator, Analyst, and Admin with View Runs, Deploy Agents, Edit Tools, and Export Logs.
Connector Registry cards: Email, Slack, REST API, PostgreSQL, SharePoint, and ServiceNow. Invoice Intake also binds Slack, Email, and ERP on the Trigger card.
Send a one-page brief naming which of Finance, Support, or Operations will own the first workspace, and whether Invoice Parser, Ticket Router, or Inventory Watcher is the first agent to evaluate.
Name the first workspace (Finance, Support, or Operations) and the first agent. Portly AI LLC replies with module scope mapped to the consoles on this page.