# What are the two API surfaces?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

GilbPlatform has two HTTP surfaces for data: the app API, /lws/..., for records, and the native API, /base/..., for sign-in, vaults, vocabulary and search.

## Deeper

Also asked:

What is the difference between the /lws and the /base API? /lws is the app API for the records of a vault: read, write, list and keep in step. /base is the native API for sign-in, making vaults, the vocabulary and search. Both reach the same records under the same access rules.

Is GilbPlatform a Solid server? Can I use Solid libraries with /lws? /lws follows the W3C draft Linked Web Storage, with JSON-LD bodies. The guide does not call GilbPlatform a Solid server and does not say Solid libraries work with it; sign-in is GilbPlatform's own.

An API surface is a set of web addresses a program calls to work with GilbPlatform. The app API, under /lws/, reads, writes, lists and keeps in step the records of a vault, and the Developer Guide uses it. File bytes have their own addresses, under /files/ and /lws/vault/&lt;vault\>/files. The native API, under /base/, is where a person signs in, a vault is made, and the vocabulary and the search are.

A call with a DPoP token carries [a new DPoP proof](http://support.gilb.com/help/how-do-i-make-a-dpop-proof-for-each-request) for each request. A DPoP proof is a short signed note your app makes for one request, naming its method and address \(RFC 9449\). On /base/ addresses the token goes in Authorization: DPoP with a new proof. The routes that sign a person in, trade tokens, register an app or run the AI chat take nothing else: a plain Bearer token there is treated as coming from no one. Many other /base/ routes, such as search, writes to a record at its own address, relation reads and the connect routes, also take a plain Bearer token, as /lws/ and /files/ do; GilbPlatform's own web apps use it. /lws/ and /files/ take both; a Bearer token is sent alone, with no proof. A malformed token is not treated as no one: on a /lws/ read it answers 401 "Malformed access token: Invalid JWT".

Both surfaces reach the same records under the same access rules: choosing one gives no access the other does not. An app's server that was given access to a vault calls them with its own token.

The full reference is the Developer Guide, GilbPlatform's guide for people who build apps on it, in its chapters Dev.Guide.Overview, https://appbuilder.gilb.com/base/e/06gkzpwebxv8ncqr4qd7egmt58, and Dev.Guide.SignIn, https://appbuilder.gilb.com/base/e/06gkzpwhanxrh55sca1pdkxj88. It can be read with no sign-in, as data for programs and AIs rather than as a web page.

Source: Dev.Guide.Overview \(A 06gkzpwebxv8ncqr4qd7egmt58, 2026-11-11; read for agreement, not copied\) Surfaces \(the table: App API /lws/..., File bytes /files/... and /lws/vault/&lt;vault\>/files, Native API /base/... "Sign-in, vault creation, vocabulary, search"; "Every call carries a token and a fresh proof"; an app server uses its own token\); Dev.Guide.SignIn \(A 06gkzpwhanxrh55sca1pdkxj88\) Surfaces \(Malformed 401 on /lws; its Bearer sentence, "A plain Bearer there is not recognised", disagrees with the code at 498d29a0 and is not used for the page: checks 11l and 11m\). GilbPlatform 498d29a0 \(live at https://id.gilb.com/version, read 2026-11-11\): docs/BASE-DEVELOPER-GUIDE.md:2314-2350 \(team notes, §2.3, not linked: "differ only in their auth posture \(both funnel to the same datom write/read path and the same authorization gates\)"; its "five /base routes" is an undercount\), src/auth/principal.ts:51-52 \(DPoP scheme\), :197-249 \(authenticatedPrincipal: a DPoP credential, else no one\), src/auth/bearer-principal.ts:10-25 \(the Bearer floor\). Plain Bearer under /base \(which covers\): the Bearer floor \(bearerFloorSurfacePrincipal, bearerFloorWriteRequirer, bearerFloorPrincipal\) is bound in 31 route files under src/routes that serve /base paths \(at 498d29a0, 32 files use files.ts\), such as src/routes/search.ts:302 \(search\), src/routes/write.ts:74 \(PUT /base/e/:id\), src/routes/read.ts:396-405 \(the /base/e/:id/relations and /base/r/:id/relations reads\) and the connect-\* route files; DPoP only: the single-record read and its history \(src/routes/read.ts:210, :513, authenticatedPrincipal; so the page says "relation reads", not record reads\), src/routes/ai-chat.ts \(DPoP-mandatory\), src/routes/ai-subscription.ts, src/routes/machine-token.ts, src/routes/client-registration.ts, POST /base/vault/create-named \(src/routes/vault.ts:363-408\); live probes of check 11m \(2026-11-11\): /base/search reads a Bearer \(401 "Malformed access token"\), /base/ai/agents/mine does not \("no token presented"\), src/routes/write.ts, src/lws/routes.ts:575 \(GET /lws/r/:id\). GilbVeda: no term for an API surface \(public read https://veda.gilb.com/base/terms?q=ApiSurface 2026-11-11: 0\). Row: Developer.TwoApiSurfaces \(its "full power" and "first-party apps" wording is not used: the published chapters say what each surface is for\).
