{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the Gateway API?","acceptedAnswer":{"@type":"Answer","text":"It is the REST service of the Forest Gateway, served by your Forest back-end. Interfaces people click in use it to read and edit records, browse relations and run Forest Actions. AI agents connect to the other service of the same Gateway, the MCP server."}},{"@type":"Question","name":"Which interfaces can use it today?","acceptedAnswer":{"@type":"Answer","text":"The Forest app for Zendesk runs on it out of the box. Any interface your team builds can call it from an allowed browser origin, and any server can call it with a service account token."}},{"@type":"Question","name":"Can our ops vibecode an interface on it?","acceptedAnswer":{"@type":"Answer","text":"Yes. Turn on the OpenAPI document and hand it to your AI coding tool. An engineer adds the app's origin to the allowed list once, then each user signs in with their Forest account and works under their own role."}},{"@type":"Question","name":"Can an interface change data without going through Forest's rules?","acceptedAnswer":{"@type":"Answer","text":"No. The Gateway API reads and edits records and runs your actions, and every call is checked against the caller's role and written to your activity log."}},{"@type":"Question","name":"How do permissions work in an interface built on it?","acceptedAnswer":{"@type":"Answer","text":"Every call reaches your back-end as the signed-in user, or as the service account whose token it carries, and the answer is filtered by that identity's role. Your interface can hide a button; the back-end makes the decision."}},{"@type":"Question","name":"Gateway API or MCP server: which one do I need?","acceptedAnswer":{"@type":"Answer","text":"The Gateway API serves interfaces people click in. The MCP server serves tools AI models call. Both ship in the Forest Gateway, apply the same roles and write to the same activity log, and you can turn on one or both."}},{"@type":"Question","name":"Does it work with a Ruby back-end?","acceptedAnswer":{"@type":"Answer","text":"Yes, through the standalone Gateway, which serves the same routes from its own process. On a Node.js back-end, the Gateway runs inside the back-end itself."}},{"@type":"Question","name":"Does customer data leave our environment?","acceptedAnswer":{"@type":"Answer","text":"The Gateway API runs with your Forest back-end, inside your infrastructure, and reads your databases in place. The AI relay behind suggested actions in Zendesk sends ticket fields and action names to Forest's AI proxy, never the records your team browses."}}]}