What is an API, and does my app need one?
Checked against GilbApp d529620.
An API is how one program asks another for data; your app uses GilbPlatform's, and your AI handles it, so you need not build one.
Deeper
API stands for application programming interface. It is a set of web addresses that one program calls to ask another program for data, or to have it do something. A person does not use it; a program does. For example, a weather service's API gives a program the weather for a place.
Your app uses GilbPlatform's API. Through it, your app signs people in and reads and writes their records in vaults, the places where a person or a group keeps their records. A record is one piece of data with its own address, such as a person, a place, a thing or a note. Agent.Coder, the agent that writes your app's code, writes the code that uses it, following the Developer Guide, GilbPlatform's guide for people who build apps on it. An agent is your AI following one written procedure, its standing instructions, for one kind of work. You do not need to learn the API yourself.
For an app that people sign in to, GilbPlatform's API needs no key from you. There are no API keys and no shared secrets, fixed strings a program would send to prove who it is: your app acts for a person with that person's token, a short-lived pass from their sign-in. (A program with its own server can sign in as itself with a registered key, but it starts with no access; the Developer Guide shows how.)
Does your app need its own API? Not to work on GilbPlatform. Its data is kept in vaults, and GilbPlatform's API already serves it to those allowed to read it. When your app goes live, it is put on the internet at https://<name>.pages.dev, a web address of its own, as only the files a browser loads: no code of your app runs on a server there. GilbPlatform sets the rules that address serves your app with, and you cannot change them: the app's pages may fetch data only from the app's own address and from GilbPlatform's own addresses, such as id.gilb.com. Pictures may also come from those two places; scripts, videos, sounds and everything else come only from the app's own files. So an app put live this way offers no API of its own to other programs, and it cannot use another company's API, such as a weather service's; the answer on connecting your app to other services says more.
Can other programs read your app's data? Not through your app: a published app offers no API of its own, as above. Your app's data is kept in vaults, and another program can read it only through GilbPlatform's API, and only what it has been given access to, as a person can. A program with its own server signs in as itself and starts with no access, as above, until it is given access to a vault; an AI connected to GilbPlatform reaches only the vaults it has been given access to; and Make public lets anyone read a vault, programs too. By default each person who uses your app keeps their things in their own vault, and whoever holds Control there decides who else may reach them. The answers How do I give my AI access to a vault? and How do I make a vault public? show how.
For developers: GilbPlatform has two sets of these addresses, one for records and one for signing in, vaults, words and search; the developer answer What are the two API surfaces? explains them. The Developer Guide starts at Dev.Guide.Overview, https://appbuilder.gilb.com/base/e/06gkzpwebxv8ncqr4qd7egmt58. It can be read with no sign-in, as data for programs and AIs rather than as a web page.
This answer is written for a computer screen.
Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:165-172 (the headers every published site gets: Content-Security-Policy default-src 'self'; img-src 'self' data: blob: https://*.gilb.com; connect-src 'self' https://*.gilb.com; Permissions-Policy geolocation=()), :21 and :146 (_headers, _worker.js and a functions folder refused: a functions folder would run your code on the server). Standard RuleDeployPagesDev (the same Content Security Policy; Call only 'self' and *.gilb.com; a built static folder). Standards: Agent.Coder.GilbStack (the Developer Guide is the public contract the code keeps). Live help pages, sentences shared: What can I build on GilbPlatform? (There are no API keys and no shared secrets; Dev.Guide.Overview address); What are the two API surfaces?; What is a record?; Where does all the code go, and can I get a copy of it? (Agent.Coder and agent glosses). Live help pages, sentences shared: How does my app's server read its own vault? (the app's server is given access to a content vault; end users get no grant); How do I give my AI access to a vault?; How do I make a vault public? (Make public lets anyone read the vault; each person's own vault is private unless they share it); How do I make sure my app is secure?. Agent.Coder (GilbStack 14a: a server registers, holds no access until the owner grants it).