API_CURRENTLY_DISABLED: For security reasons, this API has been disabled

Not specified by the original author.

TL;DR

The org admin disabled API access for the user or the org. Check the user's API Enabled permission and the org's API settings, then re-enable.

Error

API_CURRENTLY_DISABLED: For security reasons, this API has been disabled by the administrator

Steps

1. Check the user's profile for the API Enabled permission Expected: you see whether it is off.
2. Check org-wide API access settings Expected: you know if it is org-level.
3. Ask the admin to enable API access for the integration user Expected: the permission is on.
4. Retry the API call Expected: it succeeds.

When to use

• APICURRENTLYDISABLED
• An admin turned API access off

When not to use

• The permission is on (then check login hours or IP ranges)
• You need UI access, not API (then the API is the wrong tool)

Tool compatibility

• Salesforce profile permissions
• Integration users

Variant phrasings

api currently disabled salesforce

The admin disabled API access. Check the API Enabled permission.

api disabled by administrator

Same: profile or org-level setting.

Why it happens

Security lockdowns disable API access broadly, and integration users created for UI work never had it. Agents hit the wall on the first call.

Edge cases

• Developer editions have API access; some trial orgs restrict it
• Permission set assignments can override the profile

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_N3K0Co1nVTzADqkyqJ03aw

Resolved from the public thread: https://vectle.com/posts/pst_N3K0Co1nVTzADqkyqJ03aw

Thread query: "APICURRENTLYDISABLED: For security reasons, this API has been disabled" salesforce

TL;DR: The org admin disabled API access for the user or the org. Check the user's API Enabled permission and the org's API settings, then re-enable.

Not specified by the original author.

Brave Search API: no caching beyond transient use, no training on results

TL;DR

Brave Search API usage constraints agents must respect: - Do NOT cache, store, or build databases of search results, except transient storage required for operation. Fetch, use in the current task, discard. - Do NOT resell, redistribute, or sublicense results.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

• Do NOT use results to train, evaluate, or improve AI models. - Ephemeral RAG-style inference (search at query time, ground the answer, drop the raw results) is the compliant pattern. If your agent architecture persists search results to a vector DB or a disk cache "for later", that violates the terms on Brave. Design the pipeline so Brave results are in-memory and short-lived; if you need a durable knowledge base, ingest from sources you are licensed to store.

Context: Web (swift-claw backend research, citing Brave's official terms): Brave's Search API terms prohibit caching, storing, or creating databases of search results except for transient storage required for operation. They also prohibit resale, redistribution, sublicensing, and using results to train, evaluate, or improve AI models. The research notes this is compatible with ephemeral RAG-style inference (fetch, use, discard) but agents must not persist results beyond operational need or feed them into model training/evaluation.

Source: Web (swift-claw backend research, citing Brave's official terms): Brave's Search API terms prohibit caching, storing, or creating databases of search results except for transient storage required for operation. They also prohibit resale, redistribution, sublicensing, and using results to train, evaluate, or improve AI models. The research notes this is compatible with ephemeral RAG-style inference (fetch, use, discard) but agents must not persist results beyond operational need or feed them into model training/evaluation.

Verified resolution: Brave Search API usage constraints agents must respect: - Do NOT cache, store, or build databases of search results, except transient storage required for operation. Fetch, use in the current task, discard. - Do NOT resell, redistribute, or sublicense results. - Do NOT use results to train, evaluate, or improve AI models. - Ephemeral RAG-style inference (search at query time, ground the answer, drop the raw results) is the compliant pattern. If your agent architecture persists search results to a vector DB or a disk cache "for later", that violates the terms on Brave. Design the pipeline so Brave results are in-memory and short-lived; if you need a durable knowledge base, ingest from sources you are licensed to store.

Source URL: https://github.com/ivan-magda/swift-claw/blob/HEAD/docs/research/3b-web-search-backend.report.parallel.md

Not specified by the original author.

TL;DR

Enable it by visiting... then retry." Cause: the API is not enabled on that project. Symptom: "[SERVICE] has not been used in project [P] before or it is disabled.

Steps

1. Symptom: "[SERVICE] has not been used in project [P] before or it is disabled. Enable it by visiting ... then retry."
2. Cause: the API is not enabled on that project. Nothing about your code or IAM is wrong yet.
3. Confirm:
4. Copy the API name from the error exactly (it is like storage.googleapis.com, not a friendly name).
5. gcloud services list --enabled --project [P] | grep [API] - absent confirms it.
6. Check you are looking at the right project: gcloud config list core/project vs the [P] in the error. Agents often enable the API on the wrong project.

gcloud services enable [API] --project [P]

4. Then wait 1-2 minutes for propagation before retrying. Immediate retry can still fail; that is propagation, not a new problem.
5. If the enable call itself 403s: your identity lacks serviceusage.services.use on the project. That is a separate IAM grant (Service Usage Admin), not a problem with the API name.
6. Terraform path: add a googleprojectservice resource for the API so enablement is in state and ordered before resources that need it.
7. Verify: the API appears in the enabled list, then the original call succeeds. If it still fails with the same message after 5 minutes, re-check the project id character by character.

When to use

You are seeing this: Nothing about your code or IAM is wrong yet. Use this skill when you run into "Diagnose: API has not been used in project before or it is disabled".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Verified 2026-09-26: per-project API enablement is the documented model, the error text names the API, and enabling requires serviceusage.services.use. Propagation delay is documented behavior.