Skip to main content
Glama

update_endpoint

Destructive

Update an endpoint immediately or in its line draft. The patch is merged field-by-field. Requires edit access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patchYesPartial endpoint document — same shape as create_endpoint, every field optional.
lineKeyYesThe line key.
commitModeNoDefaults to publish. Draft writes require draftRevision.
endpointIdYesThe endpoint UUID.
scheduledAtNoCompatibility alias: stage this update then schedule its line.
draftRevisionNoCurrent line draft revision, required for draft writes.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / patch / properties / targets / items / properties / callbackURL
      Added value: +{
      +  "description": "Pushed once this target's delivery reaches a terminal status — see get_receipts' callbackState. Must be https. Meaningful for async targets only — refused on sync/stream. Cannot point back into this project (the same relay-loop rule as targetUrl) and must be inside the project's outbound host allowlist when one is set. Unset = the customer polls the receipt instead.",
      +  "format": "uri",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / patch / properties / targets / items / properties / answerVariants / description
      Previous value: -"The conditional form of answerMapping, for a target whose answers do not all share one shape: one mapping per reply instead of one for every reply. Requires \"distinguishBy\" naming the single thing that tells them apart ({\"source\":\"status\"}, {\"source\":\"header\",\"name\":…} or {\"source\":\"bodyField\",\"path\":…}), \"variants\" as an object keyed by the value it matches — an exact status like \"429\", a class like \"4XX\", or \"default\" — each holding a tree in the same grammar as answerMapping, and \"onNoMatch\", which has no default and must be either \"passthrough\" (hand the vendor's answer back untouched) or \"fail\" (answer 422 naming the value that matched nothing). Mutually exclusive with answerMapping on this target, and refused on a stream target for the same reason answerMapping is. A variant whose tree does not compile is refused when the line is published, not silently dropped. null = no reshaping."New value: +"The conditional form of answerMapping, for a target whose answers do not all share one shape: one mapping per reply instead of one for every reply. Requires \"distinguishBy\" naming the single thing that tells them apart ({\"source\":\"status\"}, {\"source\":\"header\",\"name\":…} or {\"source\":\"bodyField\",\"path\":…}), \"variants\" as an object keyed by the value it matches — an exact status like \"429\", a class like \"4XX\", or \"default\" — each holding a tree in the same grammar as answerMapping — or, where the caller should be answered with a status of your own, an object {\"mapping\": <tree>, \"replyStatus\": 402} — and \"onNoMatch\", which has no default and must be either \"passthrough\" (hand the vendor's answer back untouched) or \"fail\" (answer 422 naming the value that matched nothing). A replyStatus is what the caller sees and never what the delivery is measured or charged as; it must be a status that can carry a body (200–599, excluding 204, 205 and redirects), and setting one drops the vendor's own response headers, which describe the answer it replaced. A variant keyed on a status that carries no body (204, 205, 304) is reachable only when it sets one. Mutually exclusive with answerMapping on this target, and refused on a stream target for the same reason answerMapping is. A variant whose tree does not compile is refused when the line is published, not silently dropped. null = no reshaping."
  3. Changed1 schema field changed
    • addedInput schema / properties / patch / properties / attributes / items / properties / forwarding
      Added value: +{
      +  "description": "Only meaningful for in=query or in=path. blocked (default): validated, never sent to the target. forwardInPlace: sent to the target in the same location — a query attribute as a query parameter, a path attribute as a path segment. A path attribute forwards only when its name is its own zero-based segment position (\"0\" for the first segment after the endpoint URL, \"1\" for the next, …) — path segments are matched positionally, not by name. To carry a value into the body or a header instead, leave this blocked and add a field mapping on the target sourced from this attribute.",
      +  "enum": [
      +    "blocked",
      +    "forwardInPlace"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / patch / properties / targets / items / properties / answerVariants
      Added value: +{
      +  "description": "The conditional form of answerMapping, for a target whose answers do not all share one shape: one mapping per reply instead of one for every reply. Requires \"distinguishBy\" naming the single thing that tells them apart ({\"source\":\"status\"}, {\"source\":\"header\",\"name\":…} or {\"source\":\"bodyField\",\"path\":…}), \"variants\" as an object keyed by the value it matches — an exact status like \"429\", a class like \"4XX\", or \"default\" — each holding a tree in the same grammar as answerMapping, and \"onNoMatch\", which has no default and must be either \"passthrough\" (hand the vendor's answer back untouched) or \"fail\" (answer 422 naming the value that matched nothing). Mutually exclusive with answerMapping on this target, and refused on a stream target for the same reason answerMapping is. A variant whose tree does not compile is refused when the line is published, not silently dropped. null = no reshaping.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / patch / properties / targets / items / properties / answerMapping
      Added value: +{
      +  "description": "Reshapes this target's answer into what the caller receives — a tree of typed nodes conforming to the same published grammar as outgoingMapping. Refused on a stream target (deliveryMode=stream) — a stream's response is proxied straight through and never reshaped. null = no reshaping, the answer reaches the caller verbatim; paths, types and cycles are checked server-side.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / outgoingMapping
      Added value: +{
      +  "description": "Reshapes the request into what this target expects — a tree of typed nodes conforming to the published grammar at \"https://schemas.echorelay.dev/transform/mapping/v1.json\" (its own $schema key must name that value). Mutually exclusive with mapping and transformers on this target, and with the endpoint's own transformers — the write is rejected if both are set. null = no reshaping (today's behaviour, and the only value this schema itself can validate; paths, types and cycles are checked server-side).",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  6. Changed4 schema fields changed
    • changedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / description
      Previous value: -"Async retry policy. Ignored unless deliveryMode=async. Leave it unset (null) and the platform's own default ladder applies instead — it is not expressible through this schema and runs considerably longer than any maxAttempts you can set here, so a target left on defaults can sit quietly for a long time before anything reaches the DLQ. Set it explicitly — a low maxAttempts included — for a retry ladder you can predict and observe. get_endpoint reports which is in effect: this object when set, null when the platform default applies."New value: +"Async retry policy. Ignored unless deliveryMode=async. Leave it unset (null) and the platform default applies, which behaves the same as maxAttempts at its maximum. get_endpoint reports which is in effect: this object when set, null when the platform default applies."
    • addedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / properties / backoffMultiplier / description
      Added value: +"How sharply the gap between tries widens. Higher spends the same attempts over a longer stretch. Defaults to 2.0."
    • changedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / properties / maxAttempts / description
      Previous value: -"Including the initial attempt. Only takes effect when retryPolicy itself is set — see its description for what an unset retryPolicy uses instead."New value: +"Total delivery attempts, counting the first. 1 fails fast: one try, then the dead-letter queue. Higher values keep retrying with a widening gap between tries — at the default backoffMultiplier, roughly under a minute at 4, a few minutes at 7, about an hour at 10, a few hours at 14. Anything still undelivered lands in the dead-letter queue. Defaults to 14."
    • changedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / properties / maxAttempts / maximum
      Previous value: -10New value: +14
  7. Changed2 schema fields changed
    • changedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / description
      Previous value: -"Async retry policy. Ignored unless deliveryMode=async."New value: +"Async retry policy. Ignored unless deliveryMode=async. Leave it unset (null) and the platform's own default ladder applies instead — it is not expressible through this schema and runs considerably longer than any maxAttempts you can set here, so a target left on defaults can sit quietly for a long time before anything reaches the DLQ. Set it explicitly — a low maxAttempts included — for a retry ladder you can predict and observe. get_endpoint reports which is in effect: this object when set, null when the platform default applies."
    • changedInput schema / properties / patch / properties / targets / items / properties / retryPolicy / properties / maxAttempts / description
      Previous value: -"Including the initial attempt."New value: +"Including the initial attempt. Only takes effect when retryPolicy itself is set — see its description for what an unset retryPolicy uses instead."
  8. Changed2 schema fields changed
    • addedInput schema / properties / patch / properties / targets / items / properties / transformers
      Added value: +{
      +  "description": "Request transformation pipeline applied to this target before delivery. Empty array = no transformation.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "params": {
      +        "additionalProperties": false,
      +        "description": "Only the keys the chosen type reads are accepted; see the type description above.",
      +        "properties": {
      +          "field": {
      +            "description": "Target field — removeField / mapValue.",
      +            "type": "string"
      +          },
      +          "from": {
      +            "description": "mergeFields (all sources) / renameField (first element is the source).",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "mapping": {
      +            "additionalProperties": {
      +              "type": "string"
      +            },
      +            "description": "Value lookup table — mapValue.",
      +            "type": "object"
      +          },
      +          "maxSizeMB": {
      +            "description": "Max upload size in MB — binaryToUrl.",
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          "separator": {
      +            "description": "Join separator — mergeFields (default \" \").",
      +            "type": "string"
      +          },
      +          "to": {
      +            "description": "Destination field — mergeFields / renameField / addField.",
      +            "type": "string"
      +          },
      +          "ttlSeconds": {
      +            "description": "Temp file lifetime in seconds — binaryToUrl.",
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          "value": {
      +            "description": "Constant value to set — addField.",
      +            "type": "string"
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": {
      +        "description": "mergeFields: from+to(+separator). renameField: from+to. removeField: field. addField: to+value. mapValue: field+mapping. binaryToUrl: ttlSeconds?+maxSizeMB? (both clamped server-side — omit for the server default).",
      +        "enum": [
      +          "mergeFields",
      +          "renameField",
      +          "removeField",
      +          "addField",
      +          "mapValue",
      +          "binaryToUrl"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / patch / properties / transformers
      Added value: +{
      +  "description": "Endpoint-level request transformation pipeline, applied before any target-level transformers. Set to null to remove the override and inherit the line default (if the line has one); set to an empty array to explicitly apply no transformation even when the line has a default. Omit on update_endpoint to leave the existing value unchanged.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "params": {
      +        "additionalProperties": false,
      +        "description": "Only the keys the chosen type reads are accepted; see the type description above.",
      +        "properties": {
      +          "field": {
      +            "description": "Target field — removeField / mapValue.",
      +            "type": "string"
      +          },
      +          "from": {
      +            "description": "mergeFields (all sources) / renameField (first element is the source).",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "mapping": {
      +            "additionalProperties": {
      +              "type": "string"
      +            },
      +            "description": "Value lookup table — mapValue.",
      +            "type": "object"
      +          },
      +          "maxSizeMB": {
      +            "description": "Max upload size in MB — binaryToUrl.",
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          "separator": {
      +            "description": "Join separator — mergeFields (default \" \").",
      +            "type": "string"
      +          },
      +          "to": {
      +            "description": "Destination field — mergeFields / renameField / addField.",
      +            "type": "string"
      +          },
      +          "ttlSeconds": {
      +            "description": "Temp file lifetime in seconds — binaryToUrl.",
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          "value": {
      +            "description": "Constant value to set — addField.",
      +            "type": "string"
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": {
      +        "description": "mergeFields: from+to(+separator). renameField: from+to. removeField: field. addField: to+value. mapValue: field+mapping. binaryToUrl: ttlSeconds?+maxSizeMB? (both clamped server-side — omit for the server default).",
      +        "enum": [
      +          "mergeFields",
      +          "renameField",
      +          "removeField",
      +          "addField",
      +          "mapValue",
      +          "binaryToUrl"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  9. Changed4 schema fields changed
    • addedInput schema / properties / commitMode
      Added value: +{
      +  "description": "Defaults to publish. Draft writes require draftRevision.",
      +  "enum": [
      +    "draft",
      +    "publish"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / draftRevision
      Added value: +{
      +  "description": "Current line draft revision, required for draft writes.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / patch / properties / httpMethod / description
      Previous value: -"HTTP method callers must use."New value: +"HTTP method callers must use. GET endpoints cannot declare a body attribute (see attributes[].in)."
    • changedInput schema / properties / scheduledAt / description
      Previous value: -"Optional ISO-8601 time between 2 minutes and 7 days from now. When present, freeze this update for scheduled publish instead of publishing now."New value: +"Compatibility alias: stage this update then schedule its line."
  10. Changed1 schema field changed
    • changedInput schema / properties / scheduledAt / description
      Previous value: -"Optional ISO-8601 time within 7 days. When present, freeze this update for scheduled publish instead of publishing now."New value: +"Optional ISO-8601 time between 2 minutes and 7 days from now. When present, freeze this update for scheduled publish instead of publishing now."
  11. Changed1 schema field changed
    • addedInput schema / properties / scheduledAt
      Added value: +{
      +  "description": "Optional ISO-8601 time within 7 days. When present, freeze this update for scheduled publish instead of publishing now.",
      +  "type": "string"
      +}
  12. Changed1 schema field changed
    • changedInput schema / properties / patch / properties / targets / items / properties / credentialVaultEntryId / description
      Previous value: -"References a saved credential (see list_credentials/create_credential) instead of inline auth — the auth field above is ignored when this is set. Must belong to the same project."New value: +"References a saved credential (see list_credentials/create_credential) instead of inline auth — the auth field above is ignored when this is set. Must belong to the same project. The credential is bound to a destination when it is created: targetUrl must be https and its host must match that credential's destinationHost, or the write is rejected."
  13. Changed7 schema fields changed
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / description
      Previous value: -"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret."New value: +"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret. Ignored when credentialVaultEntryId is set."
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / headerName
      Added value: +{
      +  "description": "Required when type=apiKeyHeader.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / key
      Added value: +{
      +  "description": "Required when type=apiKeyHeader or type=apiKeyQuery or type=publicPrivateKey.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / paramName
      Added value: +{
      +  "description": "Required when type=apiKeyQuery.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / secret
      Added value: +{
      +  "description": "Required when type=publicPrivateKey.",
      +  "type": "string"
      +}
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / properties / type / enum
      Previous value: -[
      -  "none",
      -  "bearer",
      -  "basic"
      -]New value: +[
      +  "none",
      +  "bearer",
      +  "basic",
      +  "apiKeyHeader",
      +  "apiKeyQuery",
      +  "publicPrivateKey"
      +]
    • addedInput schema / properties / patch / properties / targets / items / properties / credentialVaultEntryId
      Added value: +{
      +  "description": "References a saved credential (see list_credentials/create_credential) instead of inline auth — the auth field above is ignored when this is set. Must belong to the same project.",
      +  "type": "string"
      +}
  14. Changed7 schema fields changed
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / description
      Previous value: -"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret. Ignored when credentialVaultEntryId is set."New value: +"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret."
    • removedInput schema / properties / patch / properties / targets / items / properties / auth / properties / headerName
      Removed value: -{
      -  "description": "Required when type=apiKeyHeader.",
      -  "type": "string"
      -}
    • removedInput schema / properties / patch / properties / targets / items / properties / auth / properties / key
      Removed value: -{
      -  "description": "Required when type=apiKeyHeader or type=apiKeyQuery or type=publicPrivateKey.",
      -  "type": "string"
      -}
    • removedInput schema / properties / patch / properties / targets / items / properties / auth / properties / paramName
      Removed value: -{
      -  "description": "Required when type=apiKeyQuery.",
      -  "type": "string"
      -}
    • removedInput schema / properties / patch / properties / targets / items / properties / auth / properties / secret
      Removed value: -{
      -  "description": "Required when type=publicPrivateKey.",
      -  "type": "string"
      -}
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / properties / type / enum
      Previous value: -[
      -  "none",
      -  "bearer",
      -  "basic",
      -  "apiKeyHeader",
      -  "apiKeyQuery",
      -  "publicPrivateKey"
      -]New value: +[
      +  "none",
      +  "bearer",
      +  "basic"
      +]
    • removedInput schema / properties / patch / properties / targets / items / properties / credentialVaultEntryId
      Removed value: -{
      -  "description": "References a saved credential (see list_credentials/create_credential) instead of inline auth — the auth field above is ignored when this is set. Must belong to the same project.",
      -  "type": "string"
      -}
  15. Changed7 schema fields changed
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / description
      Previous value: -"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret."New value: +"Outbound auth applied to the request. On reads, secrets are redacted to \"***\" — round-trip the sentinel to keep the stored secret. Ignored when credentialVaultEntryId is set."
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / headerName
      Added value: +{
      +  "description": "Required when type=apiKeyHeader.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / key
      Added value: +{
      +  "description": "Required when type=apiKeyHeader or type=apiKeyQuery or type=publicPrivateKey.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / paramName
      Added value: +{
      +  "description": "Required when type=apiKeyQuery.",
      +  "type": "string"
      +}
    • addedInput schema / properties / patch / properties / targets / items / properties / auth / properties / secret
      Added value: +{
      +  "description": "Required when type=publicPrivateKey.",
      +  "type": "string"
      +}
    • changedInput schema / properties / patch / properties / targets / items / properties / auth / properties / type / enum
      Previous value: -[
      -  "none",
      -  "bearer",
      -  "basic"
      -]New value: +[
      +  "none",
      +  "bearer",
      +  "basic",
      +  "apiKeyHeader",
      +  "apiKeyQuery",
      +  "publicPrivateKey"
      +]
    • addedInput schema / properties / patch / properties / targets / items / properties / credentialVaultEntryId
      Added value: +{
      +  "description": "References a saved credential (see list_credentials/create_credential) instead of inline auth — the auth field above is ignored when this is set. Must belong to the same project.",
      +  "type": "string"
      +}
  16. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructiveHint=true, so the mutation nature is known. The description adds valuable context: the 'patch is merged field-by-field' (how changes apply), 'immediately or in its line draft' (commit mode), and 'requires edit access' (permission requirement). These go beyond the annotation and clarify consequences without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences with zero filler. The main action and mode are front-loaded, followed by merge semantics and permission. No redundancy with schema content; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with a very detailed schema, the description covers the high-level behaviors an agent needs to decide when to call it: update action, dual modes, merge semantics, and access requirement. While it does not describe return values, output schema is absent and the schema itself carries the detailed field semantics, so this is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds meaning about the patch parameter's merge behavior and the lineKey/commitMode interplay ('immediately or in its line draft'). This enriches understanding of how parameters relate, which the schema alone does not fully convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Update') and resource ('an endpoint'), and specifies two modes: immediate or line draft. This clearly distinguishes it from create_endpoint (new endpoint) and delete_endpoint (removes endpoint), and from draft-specific tools like discard_draft_endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it: to modify an existing endpoint, either immediately or via its line draft. It mentions the merge behavior but does not explicitly exclude alternatives or state when to prefer create vs update. The two modes are clear, but there is no explicit guidance against using this for creation/deletion. Still, the context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools target distinct resources and the descriptions are unusually explicit, but the billing cluster (change_plan/cancel_subscription and the many add-on actions) plus the preview/diff tools overlap and could cause mis-selection. config_diff, dry_run_endpoint, and preview_line_draft all read as 'preview what will change' at first glance despite different scopes.

Naming Consistency4/5

The overwhelming majority follow a clean snake_case verb_noun pattern: create_*, get_*, list_*, set_*, update_*, delete_*. It is only held back by a few naming outliers such as config_diff and default_endpoint_template, which break the verb-first convention.

Tool Count1/5

78 tools is an extreme mismatch for an MCP server surface, even accounting for the broad management/relay domain. Such a large surface will overwhelm model context and make tool selection materially harder; this would be better split into focused servers for configuration, data-plane operations, and billing.

Completeness4/5

The tool surface is very thorough: projects, lines, endpoints, credentials, keys, configs/drafts, DLQ, requests, metrics, audit, team, and billing are all represented. Only minor gaps exist, such as no direct single-line get/update and the intentional inability to widen the outbound allowlist or lift archive protection via API.

Resources