API Reference

This page is the reference for every API behind Intelligence:

• the gRPC-web services, from the protos in grpc/operators/core/api/proto/runink/core/{atlas,ask}/v1/;
• the policy class of each RPC, from atlasPolicies in internal/console/atlas_grpc.go;
• the Intelligence JSON routes, from registerRoutes in internal/console/console.go.

Transport

The Atlas services and Ask are served as gRPC-web inside the console process:

• Same origin and session. They share the origin of the Flutter bundle and the session cookie of every /api/* call. There is no separate port and no mux pattern: the / handler recognises a gRPC-web request by content type (serveAtlasGRPCWeb) and hands it to an in-process grpc.Server wrapped by improbable’s grpcweb.
• No CORS. The origin function grants none. A request whose Origin names another site gets HTTP 403 cross-origin gRPC-web is not served by the console.
• One identity lookup. The session cookie is read once in the HTTP layer (sessionEmail) and carried on the request context. With sign-in configured, a call without a valid session is UNAUTHENTICATED (unauthorized — the console session is not valid; sign in again).
• Message cap. One message may be up to 16 MiB.
• Reading failures are not errors. “We could not look” is a normal response with provenance.source = DATA_SOURCE_UNAVAILABLE and an unmeasured[] reason. Error statuses are reserved for bad requests (INVALID_ARGUMENT, NOT_FOUND, FAILED_PRECONDITION), refusals (UNAUTHENTICATED, PERMISSION_DENIED) and UNIMPLEMENTED.

Classes (see Rule governance):

• read: any admitted identity.
• attributable: a session on a console with sign-in.
• decider: attributable, and then the handler enforces four eyes.
• admin: CORE_ATLAS_ADMINS.

A method missing from the table is admin-write.

CapexService (runink.core.atlas.v1)

GovernanceService

WorkspaceService

PlaybookService

ResolveService (deprecated alias) and EstateService

runink.core.atlas.v1.ResolveService stays registered for one release. The page itself uses runink.ui.estate.v1.EstateService (from org-runink/ui). The two share classes and audit actions.

The four dialing requests and PullFeed carry an optional runner field. See Resolve.

AskService (runink.core.ask.v1)

Any other streaming method is refused: the console serves no streaming RPCs except AskService/Ask.

Intelligence HTTP routes

These routes return JSON. The GET reports answer 200 even when they could not read their source, and say so in the body as source:"unavailable" / complete:false, with an unmeasured[] list.

A read and a machine ingest are deliberately registered as separate exact paths, not one handler switching on the method. A guard applied to the wrong verb is how this kind of code goes wrong quietly. /api/data-governance-findings is the one exception: both verbs act on the same findings store, so the split happens inside the handler.

Token-door errors: