Connect AI to Your Systems.
No SDK. No new skills. Your team builds with what they already know.
“Create a purchase order for 500 units of oak veneer”
Answered with live data from your
How It Works
Three concepts. No SDK. No middleware.
Describe
Write a JSON manifest listing your operations. Each one gets a name, a description the AI can read, input parameters, and a risk level. That's the entire contract.
Connect
Your bridge opens a persistent encrypted tunnel to SynthGrid. No inbound ports. No public endpoints. SynthGrid sends operation requests; your bridge executes them against your systems and returns results.
Deploy
Users talk to SynthGrid in natural language. The AI reads your manifest, picks the right operations, fills in the parameters, and calls your bridge. Adding new operations is the same process — write the JSON, add the handler.
The Protocol
This is everything SynthGrid needs to understand a new operation.
{
"name": "create_purchase_order",
"description": "Creates a new purchase order in the ERP system. Requires a vendor, at least one line item, and a project code.",
"route": "/action/create_purchase_order",
"riskLevel": "humanApprovalRequired",
"input": {
"type": "object",
"properties": {
"vendor_code": { "type": "string", "description": "ERP vendor identifier" },
"project_code": { "type": "string", "description": "Cost center or project code" },
"line_items": { "type": "array", "description": "Items to order with quantities" },
"notes": { "type": "string", "description": "Optional notes for the PO" }
},
"required": ["vendor_code", "project_code", "line_items"]
}
}Human-readable descriptions
The AI reads these to understand when and how to use each operation. Write them like you'd explain the operation to a new team member.
Risk levels
Set riskLevel per action: safe, machineApprovalRequired, humanApprovalRequired, or forbidden. SynthGrid enforces the workflow before executing.
JSON Schema input
Standard JSON Schema for input validation. SynthGrid validates parameters before calling your bridge. Your code receives clean, typed data every time.
Freeform output + html_view
Return any JSON in data. Optionally include an html_view string — SynthGrid renders it as a rich card. Purchase orders, customer profiles, reports — formatted for humans, not machines.
This is the entire integration surface. No SDK. No client library. No generated stubs.
Your bridge receives JSON, calls your systems, returns JSON. That's it.
Already in Production
Fifteen minutes of data entry became ten seconds.
The situation
Mid-market manufacturer. Custom in-house ERP that runs everything — procurement, production, sales. No cloud. No API. Built and maintained by their own team over 15 years.
Before
Creating a purchase order meant navigating four screens, looking up vendor codes, cross-referencing project IDs. Fifteen minutes of data entry per order.
After
Staff tell SynthGrid what they need in plain language. The system finds the right codes, validates the data, and creates the order. Ten seconds.
48 Operations
What a single deployment looks like. Six business domains, running in production.
Procurement
10 operations- CreatePurchaseIndent
- UpdatePurchaseIndent
- GetPurchaseIndentById
- SearchPurchaseIndents
- GetPurchaseIndentsByCustomerId
- GetPurchaseIndentsByProjectId
- SearchVendors
- GetVendor
- CreateVendor
- UpdateVendor
Production
9 operations- CreateWorkOrder
- UpdateWorkOrder
- GetWorkOrder
- SearchWorkOrders
- SearchItems
- BatchSearchItems
- GetItemById
- CreateItem
- UpdateItem
Companies & Contacts
8 operations- SearchCompanies
- GetCompanyById
- CreateCompany
- AddLocation
- AddContact
- SearchErpCustomers
- GetErpCustomer
- CreateCustomer
Sales & Invoicing
10 operations- CreateProformaInvoice
- SearchSalesCustomers
- GetSalesCustomer
- UpdateCustomer
- SearchSalesProjects
- GetSalesProjectById
- SearchErpProjects
- GetErpProjectById
- CreateProject
- UpdateProject
Lead Management
7 operations- CreateLead
- UpdateLead
- AddLeadSchedule
- SearchSalesSalesPeople
- GetSalesSalesPerson
- SearchErpSalesPeople
- GetErpSalesPerson
Daily Visits
4 operations- LogDailyVisit
- GetDailyVisit
- SearchDailyVisits
- UpdateDailyVisit
Your team already has a REST API.
Add a few Fiber endpoints. That's the whole integration. The bridge is so simple that ChatGPT, Claude, or SynthGrid itself can write it in a single prompt. Most teams are live in an afternoon.
No API. No documentation. No cloud. 15 years of technical debt.
The 48 operations above came from a custom in-house ERP that had never been connected to anything. No REST endpoints to wrap — the bridge had to navigate a legacy database directly. It still worked. That's the range: from a one-prompt integration to a full-scale ERP rescue. The protocol handles both.
The protocol is the same whether your bridge is 50 lines or 12,000. Fiber doesn't care what's behind the endpoint.
Deployment Scenarios
Fiber works with whatever you already run.
Existing REST APIs
You already have internal APIs. Add a thin Fiber layer on top — a few JSON definitions, a few route handlers. Your existing code stays exactly as it is. The bridge wraps what you've already built.
Internal Databases
Connect databases that aren't exposed to the internet. No schema changes, no ORM, no API gateway. Just JSON definitions for the queries you already run. The bridge talks to localhost — nothing changes about your infrastructure.
Software Teams
Five internal tools that don't talk to each other. Each one gets its own bridge. SynthGrid orchestrates across all of them in a single conversation — querying one system, writing to another, checking a third. One natural-language interface for everything.
Legacy Systems
No API. No documentation. 15 years of technical debt. Even systems that have never been connected to anything can be brought online through Fiber. The bridge handles the complexity — the protocol stays the same.
Digital Sovereignty
No vendor code runs on your systems. Ever.
Most AI platforms require you to install their software on your infrastructure, learn their framework, and run their processes inside your network. Fiber requires none of that. The bridge is your code — written by your team, in your language, on your servers. There is nothing to install, nothing to trust on faith.
No vendor binaries
No SDK, no agent, no runtime. Your bridge is a standard HTTP server in whatever language you choose. Read every line of code that touches your systems.
Your data stays home
The bridge runs on your network. Data flows through an encrypted tunnel that your bridge initiates. No inbound connections. No cloud sync. No data at rest outside your perimeter.
Switch providers, keep your integration
Fiber Protocol is open. If you change AI platforms, your bridge code and operation definitions stay exactly the same. Zero migration cost.
Audit everything
Every operation call, every parameter, every response — logged on your infrastructure. Your compliance team can audit the full chain of custody without asking a vendor for access.
What You Don't Have to Build
Your team writes the business logic. The rest is built in.
Security
Encrypted private tunnel between SynthGrid and your network. No inbound ports. No public endpoints. Your systems stay invisible to the internet.
AI Intelligence
SynthGrid learns how to call your operations from the descriptions you provide. It handles parameter mapping, error recovery, and multi-step workflows on its own.
Approvals & Audit
Sensitive actions require human sign-off before they execute. Every action is logged with the user who authorized it, the parameters used, and the result returned.
Formatted Output
Purchase orders, customer profiles, inventory reports — they show up inside SynthGrid as formatted cards your team can read at a glance. Not raw JSON.
Version Negotiation
Update your operations without breaking anything. SynthGrid negotiates capability versions automatically. Old operations keep working while new ones come online.
Error Recovery
Timeouts, malformed responses, downstream failures — SynthGrid retries with exponential backoff, reports clear errors to users, and never corrupts your data.
The Alternative
What AI integration usually looks like versus what it could look like.
Traditional Integration
- Timeline 6–12 months
- Dependency Vendor SDK + middleware + adapters
- Deployment Public endpoints, API gateway, firewall rules
- Maintenance Breaking changes every major version
- AI Understanding Teach the AI about each system manually
- Team Required Integration consultants + vendor support contracts
SynthGrid + Fiber
- Timeline One afternoon
- Dependency JSON over HTTPS. That's it.
- Deployment Outbound tunnel. Nothing exposed.
- Maintenance Updates without breaking anything
- AI Understanding AI understands your systems automatically
- Team Required Your existing dev team
Connect Your Systems
Your team can be live this week.
We built Fiber on the skills your team already has.