The API Builder connects REST APIs and databases and puts them in one catalog. Screens built by AI never send SQL and never hold a credential. They can only call APIs in the catalog, and every call goes through the platform server for a permission check.
- REST APIs, by OpenAPI document
- Register the OpenAPI 3 document of an internal service and its operations join the catalog. Calls go out through the platform server with the credential stored on the source, encrypted and never sent to the browser. The email of the person who made the request is passed along in a header.
- Database tables as REST APIs
- Connect a database and its tables, columns, keys, lengths and allowed values are read for you. Nothing is exposed until you pick a table. Each exposed table gets list and get-one APIs, and columns that look sensitive, such as passwords and tokens, start hidden.
- Field definitions that validate
- For every field you decide its label, allowed values, length and format, whether a request may set it, and whether the response includes it. Labels are drafted from database comments, and AI can fill in the rest. The same definition validates writes and tells the Screen Builder what each field means.
- Writes are off until you turn them on
- Read connections are opened read-only where the database supports it. Create, update and delete APIs exist only after you allow writes for the source and for the table, and an app that uses them goes through publish approval.
- A name instead of an ID
- For a foreign key column, pick up to three columns of the referenced table to return with each row, so an order shows the customer name next to customer_id. Lists can be sorted and searched by them.
- Lists that hold up with real data
- Every generated list uses the same grid: header sorting and column filters that are sent to the list API, resizable and pinned columns, a sticky header, rows that expand for detail, a summary row and CSV export. AI turns these on only where the API supports them.
- New tables, with the SQL in view
- Describe the data you need and AI drafts the table, then refine it in conversation or by hand. You see the exact SQL before anything runs, in the dialect of your database. Any table shows its CREATE statement in the API definition.
- What is sent to the AI model
- The request text and attached images, the screen code and the API specifications are sent to the model provider you choose. Data that screens read is not sent, and values that appear in error messages are masked before sending. When AI drafts field definitions or SQL it sees table and column names, not rows. Sample values are sent only for field definitions, and only for columns where an admin switched that on.