zograph.
Request a walkthrough
Menu

AI agents for every team. Set up by your experts. Governed.

Security approves the models, tools and skills once. Your subject-matter experts compose them into agents for their teams without code, working across the systems you already use, and every action stays inside your rules.

Not ready to talk? Join the waitlist.

Builder Layer

Conversational and background agents from configuration: a prompt, a model allowlist, and plugins. Versioned draft to publish.

Read more →

Compose

Bring your knowledge, tools and skills together.

Govern

Control, observe and prove every action.

Run

Keep your options for models and deployment.

Works with your stack

Connect systems over MCP, other agents over A2A.

Build

Layer 01 / 08

Compose the agent your work needs.

Build conversational and background agents in Zograph Studio.

Define their instructions, attach knowledge, MCP servers, plugins and skills, and choose the capabilities and model they need.

Request a walkthrough

See Zograph in your world.

Illustrative examples

Choose an example to update the agents, tools and workflows throughout this page.

Choose a homepage example

Attach your resources

Knowledge

Give the agent access to your content.

Payment handling procedures245 pages · Updated 2 days ago

MCP Servers

Connect to your systems through MCP.

  • Payment operations systemPayment exceptions and statusconnected
  • Transaction recordsSupporting transaction contextconnected
  • Service deskRequests, notes and approvalsconnected

Plugins & Skills

Add reusable skills and tool packages.

  • Data AnalysisTables, charts, insightsconnected
  • Document GenerationWord, PDF, structured outputconnected
  • Custom SkillsYour organization’s packages

Your choice of model

Choose from supported providers and compatible endpoints.

  • Anthropic
  • OpenAI
  • Mistral

and more

Agent

Payment Operations Agent

Helps teams review payment exceptions.

Instructions

Review payment exceptions using payment status and transaction context. Prepare a briefing for the operations team and request approval before issuing a refund.

  • Knowledge
  • MCP Servers
  • Plugins & Skills
  • Add

Capabilities shown in this example

Task Planning

Let the agent plan and manage complex work.

  1. Review the payment exception
  2. Check status and transaction context
  3. Summarize unresolved questions
  4. Prepare the exception brief

Artifacts

Let the agent create and iteratively refine documents.

Payment exception brief

DOC

A briefing with payment status, transaction context and questions for the operations team.

Two ways to put agents to work.

Conversational agents

Work with an agent.

Ask questions, review its work and guide the next step through conversation.

Payment Operations Agent

You“Review payment exception PAY-3184 and prepare a brief.”

Agent“I’ve prepared the brief with payment status and supporting context.”

Background agents

Delegate work to an agent.

Run agents on a schedule or trigger them from your systems. No open conversation required.

Started by

On a scheduleorFrom your systems
WorkPayment exception review
ResultPayment exception brief ready for the operations team.

More ways to equip your agent.

  • Memory

    Keep useful context across conversations.

  • Learned Heuristics

    Apply reviewed lessons from earlier work.

  • Web Tools

    Search the web and retrieve pages.

  • Code Sandbox

    Run code in a sandboxed environment.

  • Feedback

    Collect feedback on agent replies.

  • Suggested follow-ups

    Suggest the next message in a conversation.

More capabilities are in development.

Builder / 01

02 / Evaluation

Test behavior.
Before release.

Run the scenarios that matter to your business. Inspect the response and evaluation results.

Example evaluation

Scenario

Test scenario

Payment exception review

Review the payment exception and prepare a briefing using payment status and supporting transaction records.

Agent response

Payment exception brief

The payment status, supporting transaction context and questions that need review.

Evaluation checks

  • passPayment status included
  • passSources included
  • failUncertainty flagged

Refine the agent. Run the scenarios again.

03 / Extensibility

Your logic.
In the lifecycle.

Extend Zograph with synchronous HTTP hooks and events. Work with agents on other platforms over A2A.

Synchronous hooks

Call your service and use its response.

Zograph lifecycle
HTTP requestResponse
Your service

Event subscriptions

Let your systems react to platform events.

Zograph
Platform event
Your system

Agent to agent

Delegate to agents on other platforms, or publish yours for them to call.

Zograph agent
TaskResult
External agent

Your services and other agents, connected to the platform lifecycle.

Evaluate + Extend / 02

Govern

Layer 04 / 08

See the work behind the result.

Inspect conversations and background runs, from individual tool calls to their sources and artifacts. Understand execution, model usage and time spent waiting.

Payment Operations Agent

Payment exception PAY-3184 · Example conversation

ConversationBackground run

Recorded actions

Execution

Approval wait

Continue

  1. Get the payment exceptionget_payment_exception
  2. Read payment statusget_payment_status
  3. Read transaction contextget_transaction_context
  4. Update task plantask_plan_update
  5. Issue a refundissue_refund
    Waiting for approval
  6. Edit payment exception briefartifacts_str_replace

Illustrative execution · not a time scale

Associated context

Task planPayment handling proceduresPayment exception brief

Selected action

Issue a refund

Completed

Recorded result

Refund issued.

Payment operations system · MCP tool

Approval wait35.3 s
Tool execution154 ms
Inspect recorded input and result

Permission and execution are separate facts.

Execution

Outcomes, duration and approval waits.

Usage

Models, tokens and estimated cost.

Context

Plans, sources and created artifacts.

Observability / 04

Set the rules. Control the action.

Set defaults across your agent’s tools, refine permissions by source or action, and choose when approval is required.

Configure the boundaries

Agent defaults
Source rules
Individual tools

Broad defaults. Inherited settings. Deliberate exceptions.

  1. Read payment recordsPayment operations system
    Allowed
    Administrator rule
  2. Update task planTask Planning
    Allowed
    Plugin default
  3. Edit payment exception briefArtifacts
    Allowed
    User standing grant
  4. Issue a refundPayment operations system
    Ask administrator
    Explicit tool rule
  5. Change payout destinationPayment operations system
    Denied
    Administrator rule

Governed action

Issue a refund

Example request

Administrator approval required

Effective permission

Ask an administrator each time.

Initiated by

Requesting user

The requested call is held until an administrator decides.

Rules establish permission.

Across plugins, provider tools and MCP servers.

Grants carry user authority.

Automatic allows still have a deciding source.

Your logic can participate.

Connect decision logic through an extension.

Access & Governance / 05

Every decision, with its reasons.

Keep the history of changes, tool permissions, attempted actions and approvals. Trace an action back to the rule, authority and turn behind it.

Connected records

  1. Changes

    History

    Who changed or published what.

  2. Tool permissions

    Admissions

    What was allowed, denied or required approval.

  3. Invocations

    What was attempted and how it ended.

  4. Approvals

    Who decided, and how the request was resolved.

Selected record · Invocation

Related turn

Issue a refund

Allowed following administrator approval.

Permission · AllowedExecution · Completed

Authority

Administrator approval required each time.

Explicit rule for this tool.

Approval

Approved by an administrator.

Decision recorded before tool execution.

Execution

35.3sapproval wait154msexecution

Refund issued. Outcome recorded separately from permission.

Related context

Payment Operations Agent

Initiated by the requesting user.

Inspect the associated turn

Automatic decisions, too

Edit payment exception brief

User standing grantAllowed

Not only the exceptions. The automatic allows, too.

Records that support review and accountability.

Audit & Compliance / 06

Run

Layer 07 / 08

Choose your models. Keep your options.

Use Zograph’s model access, or bring your own provider credentials. Choose from supported models and compatible endpoints, with control over the connections behind your agents.

Zograph-managed access

Model access supplied by Zograph.
No provider API key required from you.

Your own provider credentials

Connect through your own provider accounts, cloud platforms
or compatible endpoints.

One platform

zograph.

Your agents, in control.

Payment Operations Agent

  • Agent configuration
  • Governance
  • Execution records

Your platform stays the starting point.

Evaluate behavior when changing models.

Model connection options

Direct APIs

Connect directly using your provider credentials.

  • AnthropicAvailable
  • OpenAIAvailable

Cloud platforms & routing

Connect through the platform or routing service you use.

  • Amazon BedrockAvailable
  • Microsoft Foundry (Azure)Available
  • Google Cloud / Vertex AIPlanned
  • OpenRouterPlanned

Your inference endpoint

Connect a supported private or self-hosted inference service.

  • Self-hosted modelsAvailable
  • OpenAI-compatible endpointsAvailable

Additional integrations are planned. Tell us which platform your team uses.

Connection choices, not a failover sequence.

Model choice

Choose from the models your connections support.

Zograph access or your own keys

Start with Zograph-managed access, or connect your own provider account.

Compatible endpoints

Connect beyond a fixed catalog through supported interfaces.

Redundancy / 07

Your platform. Your environment.

Choose where Zograph runs and how it connects to your models and systems. Keep deployment, regional choices and external dependencies explicit.

Platform deployment

Zograph-managed

Available regions

  • European Union (EU)
  • United States (US)
zograph.

Platform

Your governed agent platform.

  • Agents
  • Governance
  • Execution records

Connected services

Inference endpoint

Your configured model connection.
Placement depends on configuration.

Business systems

Payment records, procedures and tools.

Example deployment. Model and business services sit outside the platform environment in this configuration.

Deployment choice

Where the platform is operated.

Regional choice

Where the deployment is located.

Explicit connections

Which models and systems the platform depends on.

Sovereignty / 08

Walk us through
your case.

Forty minutes with the people who built Zograph. Start with the workflow you want to govern first.

Not ready to talk? Join the waitlist.