AI assistant
Connect FazerCards to an AI assistant
FazerCards runs an MCP server, so you can attach your reseller account to an AI assistant and work in plain language: find a product, see your own price, place the order, read back the codes. You connect with a revocable link you create yourself in the panel, so your API key never has to travel anywhere. This page is the shared groundwork every client guide assumes: what the assistant can do, how the credential works, and what it costs you when it buys something.
What the assistant can actually do
Eight things, and they map one-to-one onto the public FazerCards API. It can search the catalog across gift cards, game keys and in-game top-ups. It can open a category and list the denominations with your price on your tariff and the stock behind each one. It can validate a player ID before a top-up. It can place an order, check that order later, list your recent orders, and report your balance, plan and subscription end date.
Everything it returns comes from your account through the same API you already use. There is no separate AI catalog and no second price list: if the assistant quotes a number, that number is what the order will cost you. The reverse is also true — the assistant cannot invent an offer. Order creation requires an offer id it can only have received from a real catalog call, so "buy me 500 diamonds" always turns into a lookup first.
A few product lines are deliberately not wired into the assistant yet: Steam top-ups, Telegram Stars and manual services stay in the panel and the API. If you ask for those in chat, the assistant simply will not find a tool for them.
The connection link is not your API key
When you create the connection in the panel you get a link shaped like https://api.fzr.cards/mcp/mcp_… — and the part after the last slash is a separate credential. It is issued for AI clients only, it is listed separately in your profile, and one click removes it. Your API key is untouched by all of this: revoking the link does not rotate the key, does not interrupt your integrations, and does not affect anything running against the API.
That separation exists because of where the credential ends up. A URL passes through proxy logs, browser history and whatever the client stores locally. We are not willing to let your API key sit in those places, so the server refuses it there: paste a key that starts with fc_ into the path and the request fails, by design, no matter how correct the key is. Only mcp_ tokens are accepted in a URL.
Treat the link like a password anyway. It reaches the same account with the same permissions, and anyone holding it can spend your balance. If it leaks — a shared screen, a pasted config, a synced settings file on a machine that is not yours — open the profile page, press Revoke, and the link is dead the moment you confirm. Then create a fresh one and re-add it in your client. Regenerate does both halves in one step when you just want to rotate.
Orders move real money
There is no sandbox in this flow. When the assistant places an order it charges your live balance immediately, the same as a call you would have made yourself. Game top-ups that reach the player's account cannot be pulled back, so a wrong ID is a real loss, not a support ticket. Ask for validation first and read the returned nickname or account label out loud before you approve anything.
Prices always come from your own catalog at your own tariff, including any personal markup rules on your account. The assistant does not estimate and does not remember yesterday's price — it re-reads the offer. If a number looks wrong, the fix is to ask it to fetch the offer again rather than to argue with it.
The practical habit that prevents nearly every accident: keep purchases explicit. Name the product, the denomination, the quantity and the ID in one sentence, let the assistant restate it from catalog data, and only then say yes. The order tool accepts an idempotency key, which protects a retry of the very same call — but a second, differently worded request is simply a second order.
Choosing a client, and why every one of them uses "no authentication"
Start with the part that trips everybody up: our MCP server has no OAuth. There is no consent screen, no client id, no secret, and no discovery endpoints for a client to find. So in every client you pick the option that means none — it may be labelled "No authentication", "None" or "No auth" — and you leave every OAuth field empty. If a client insists on signing you in, it is looking for something we do not publish; the credential is already in your link. Getting this wrong is the single most common reason a connection appears to fail.
Cursor is the most secure route and the one to pick if you are comfortable editing a file. You add the server to an MCP config file (a project-level .cursor/mcp.json or the global one, reachable from the MCP settings screen) and pass the token as a header, which keeps it out of the URL entirely. MCP is part of the editor rather than a paid add-on, so there is nothing extra to buy for it. The cost is that it is a developer tool and you are editing JSON by hand.
Claude is the cheapest way to start for a non-developer. Custom connectors are added from the connector settings (https://claude.ai/settings/connectors, look for "Add custom connector" or "Connect apps"), you paste the whole link, and you are done — no file, no JSON. Custom connectors work on the free plan, which is limited to a single custom connector — no other client here starts at zero cost. The token does sit in the URL, which is exactly what it was designed for.
ChatGPT suits you if that is already where you work. Custom MCP servers live in the connector settings (https://chatgpt.com/plugins, after switching on developer mode in settings), it also needs a paid plan, and the token likewise travels in the URL. Setup is a little more hidden than Claude's, and availability of the custom-server option has moved around between plan tiers, so check what your plan exposes before you buy anything for this.
Pick your assistant
The setup differs by client. Start where you already work.
How to get started
Create your connection link
Open the FazerCards panel and go to your profile page. Find the card titled "Connect to AI" and press "Create link", then "Show link" and copy it. It looks like https://api.fzr.cards/mcp/mcp_ followed by a long string. Store it the way you store a password — you can reveal it again later, but treat every copy as live access to your balance.
Choose the client that matches how you work
Decide by where the token ends up and what you are willing to set up. Choose Cursor if you want the token in a header instead of a URL and do not mind editing a JSON config; it is the most secure option and needs no paid plan. Choose Claude if you want to paste one link into a settings screen and be finished, and accept a paid plan for custom connectors. Choose ChatGPT only if you already live there, since setup is more hidden and it also requires a paid plan.
Run a read-only check before you let it spend
After connecting, ask three harmless questions in order: what is my balance and plan, find a product you know is in your catalog, and validate a real player ID for a top-up you understand. If all three return sensible live data, the connection is genuinely working end to end. Only then place a first small order, and confirm the product, quantity and ID out loud before you approve it.
What the connection link looks like
{
"mcpServers": {
"fazercards": {
"url": "https://api.fzr.cards/mcp",
"headers": {
"Authorization": "Bearer mcp_XXXXXXXX"
}
}
}
}If something goes wrong
The client keeps asking you to sign in, or reports that it cannot find an authorization server
It is looking for OAuth, which we do not run. Go back to the connection settings, select the no-authentication option, and clear any client id, secret or scope fields. If the client will not let you save without them, that client cannot connect to us in that mode.
Every tool call returns 401 or "API key required"
The credential did not arrive. Re-copy the whole link from the profile card — a truncated token is the usual cause — and check for a trailing space. If you pasted your API key into the URL instead, that is refused on purpose: only the mcp_ link works in a path.
Tools fail with an inactive-subscription message
Renew your plan in the panel. The connection itself is fine and needs no changes; calls start succeeding again immediately after renewal.
Sudden rate-limit errors during normal chatting
An assistant makes several API calls where you made one, and a single catalog question can cost up to three. Wait a minute, ask narrower questions instead of "show me everything", and contact support if your workload genuinely needs a higher ceiling.
The assistant cannot find a product you know you sell
Search matches words in the product title, so long natural phrases miss. Ask for the short brand name — "PUBG" rather than "pubg mobile uc top up" — and let the assistant list the denominations from the category it finds.
Questions
Which authentication option do I choose in my AI client?
None. Pick "No authentication" (it may be worded "None" or "No auth") and leave every OAuth field blank — client id, client secret, scopes, all of it. FazerCards does not run OAuth and publishes no discovery endpoints, so there is nothing for the client to negotiate. Your identity travels in the mcp_ link itself.
Where does my API key go in this setup?
Nowhere. The connection link carries a separate mcp_ token, and that is all a client needs. The server actively rejects a normal API key in the URL path, so pasting fc_… there will fail even though the key is valid — the path is logged in too many places for us to accept it. Keep the API key for your own server-to-server calls.
Can the assistant actually spend my money?
Yes. Placing an order charges your live balance the moment it goes through, and a delivered game top-up cannot be reversed. Clients normally ask you to approve a tool call that writes, but treat that prompt as a backstop, not as your only control: validate the player ID first, and confirm product, denomination and quantity before you say yes.
What exactly happens when I revoke the link?
It stops working immediately. Every client still configured with it starts getting rejected on the next request, so you do not need to clean anything up on their side beyond deleting the entry. Your API key, balance, orders, tariff and running integrations are all untouched. When you are ready, create a new link and paste it back in — or use Regenerate, which revokes and reissues in one step.
Is the mcp_ token the same thing as my API key?
No — different credential, issued separately, revoked separately, shown in a different place in your profile. What is the same is the account behind it and the permissions it carries, so a leaked link is as serious as a leaked key. The difference is the cleanup: killing the link costs you one click and breaks nothing else.
What happens if my subscription lapses?
The connection stays configured, but any tool that touches your account starts failing with an inactive-subscription error, exactly as the API would. Nothing is deleted and you do not need a new link — renew in the panel and the assistant works again on the next request. Read-only handshake steps may still respond, which is why a lapsed plan can look like a broken connector at first glance.