My InfraNodus API Key Is Not Working

You can use the InfraNodus API in the InfraNodus browser extension, Obsidian plugin, in the InfraNodus MCP server, or to connect it to external applications, such as n8n or Make.Com.

In order to do that, you need to register an account in InfraNodus and then obtain an API key that you will add in your user settings. 

Usually after you get the API key, everything should work straight away. You can even try the API and all information extension without the key. If you encounter a problem, there may be several solutions, depending on the situation:

Note, that we allow API use without any keys (but only for a limited number of calls), so if you need to try something out or quickly check if any of the apps / MCP server works, you can just leave the API key field empty. In this case you'll be provisioned a temporary key that will connect to your unique machine / IP signature that you can use for a short time. As it's a demo user access you won't be able to save / retrieve your saved data.

Reason #1: Did You Exceed Your Subscription's Quota?

Note, that your InfraNodus API key will have a quota designated for your subscription tier:

If you exceed this quota, your API / AI functionality in external apps (extension, Obsidian, MCP server) will stop working. 

You will have to wait for the reset time (1 hour for AI, 1 week from the first use for API) in order to start using it again OR upgrade to the next subscription tier.

If you upgrade, you need to issue a new key after the upgrade (because the old ones will use the old quota), so that your new key uses the quota of the upgraded account. Then add that new key to your application settings. 

If you're still having problems, please, contact us via Discord or support portal with your username for us to update your quota.

Reason #2: You Didn't Add the Correct Authorization Details to MCP

If you're using InfraNodus MCP server, you need to add the environmental parameter INFRANODUS_API_KEY to your LLM Client settings. 

1. In case you're using the MCP server from Smithery, you will need to add that key in two places:

1. In Smithery's own Configuration settings
2. When you connect to Smithery using OAUTH in "Additional Details" field
3. If you do not use OAUTH, you need to get a link from Smithery that has the api key of Smithery in the URL itself, so Smithery can authenticate you and connect you to the InfraNodus MCP server .

2. In case you're adding the MCP server via the `npx launcher' in the config file in your favorite LLM client, you need to add the API key like that:

 "infranodus": {
		"command": "npx",
		"args": ["-y", "infranodus-mcp-server"],
		"env": {
			"INFRANODUS_API_KEY": "YOUR_INFRANODUS_API_KEY"
		}
  }

Reason #3: Legacy API Key In Your Settings

If you used InfraNodus before 15 August 2025, you might have a legacy API key in your settings. Make sure to generate a new API key at https://infranodus.com/api-access and add it to your applications. 

Reason #4: Old Version of Obsidian Plugin

If your Obsidian plugin is not working, you might have an old version of it installed that used the old legacy API keys. You need to update your InfraNodus Obsidian plugin to the latest version in Settings > Community Plugins > InfraNodus Graph View > Update. 

Then, once updated, add the newly generated key from https://infranodus.com/api-access and relaunch Obsidian. 

If that doesn't work, you can try completely removing the extension and adding it again. 

Reason #5: Browser Extension Login Conflict

Our browser extension can use your existing InfraNodus login session but you can also provide it with an API key. 

If the extension stopped working, you can remove it and add it / update it from the Google Chrome Store / FireFox Addons / Apple App Store (for Safari iOS and MacOS). 

Then add the API key from https://infranodus.com/api-access and it will work again.

If you hit your rate limit with the extension, a good hack is to remove the key and use your logged in browser session (works in Chrome and Firefox only). In that case, you'll never hit a limit as it uses your existing InfraNodus login to access your data. 

Reason #6: Incorrect Authentication for API Access

If you use InfraNodus API in other applications (e.g. for n8n / Make.Com workflows), you need to make sure you perform Bearer authentication with the correct key. Read more about it on this page: InfraNodus API Access Points