Reference
Plain-language glossary
Technical words, explained without the technical fog.
| Term | Plain meaning |
|---|---|
| API | A defined way for one program to ask another program to do something. |
| MCP | A standard connection that lets an assistant discover and call tools. |
| OAuth | A sign-in and permission process that avoids handing an app your password. |
| PKCE | An extra check that ties a sign-in result to the program that started it. |
| Token | A short-lived pass a program sends with its request. |
| Scope | An action category a token may request, such as read or write. |
| Audience | The particular service a token is meant for. |
| Organization / tenant | A company or group whose data and permissions are kept separate. |
| Workspace | A place within an organization for a team or set of work. |
| Endpoint | The address for one API operation. |
| JSON | A common text format for structured inputs and results. |
| Schema | The rules for which fields and values a request or result may contain. |
| Run / job | One saved attempt to do some work. |
| Checkpoint | Saved progress that an eligible job can continue from. |
| Idempotency | A supported operation recognizes a repeated request and avoids doing the same change twice. |
| Provenance | The record of where a result came from: inputs, methods and versions. |
| Rollback | Returning to a previous software release. |
| Restore | Recovering saved data from a backup into a chosen destination. |
| CI/CD | Automated checks and release steps used when software changes. |
| ΔG | A calculated change in free energy, shown with its method and units. It is one piece of molecular-interaction evidence. |
Protocol references: OAuth 2.0, PKCE, MCP specification, OpenAPI.
