T3Planet Credits — QA setup guide

​

What “connected” means

1. Credits toggle is ON (credit_mode = 1 in tx_nst3af_runtime_setting)
2. At least one valid T3Planet license key exists in ns_product_license
3. Activate succeeded and a Bearer token was stored (encrypted in tx_nst3af_runtime_setting.token_enc)

​

Part A — Prerequisites

​

TYPO3 instance

• TYPO3 — 13.4+ (or the version required by the project).
• PHP — 8.2+.
• Extensions — ns_t3af plus child extensions under test (for example ns_t3ai, ns_t3aa).
• License extension — nitsan/ns-license (license rows in ns_product_license).
• Backend user — Admin, or a user with T3AF module access.

​

Network

• https://composer.t3planet.cloud/API/AI/* (Token, Balance, Charge, Stream, …)

​

T3Planet license keys

• Valid license rows in ns_product_license (T3Planet shop / license activation in TYPO3)
• License is non-expired or lifetime
• Domain binding: the install’s public hostname should match domains registered on the license (production, staging, or local as configured on T3Planet). Domain mismatches often cause token or API errors.

​

MCP + Native AI testing (optional)

• MCP mode — Native on T3AF → MCP Server tab.
• Credits — Fully active (see Part B).
• Expected aiProvider in MCP tools — Single option: t3planet_credits (T3Planet Credits (active)).

​

Part B — Connect T3Planet Credits

​

Step 1 — Start the instance

ddev start
ddev composer install

​

Step 2 — Open T3AF → AI Providers

1. Go to T3AF
2. Open the AI Providers tab

• T3Planet Credits (recommended)
• Your Own API Keys

​

Step 3 — Select T3Planet Credits

1. Click the T3Planet Credits card
2. Confirm the switch dialog (Switch to T3Planet Credits)
3. Expect a notice such as: Credits mode selected. Click Activate to connect your license.

​

Step 4 — Activate (required)

1. Click Activate (on the T3Planet Credits card or dashboard toolbar)
2. The system will:
   • Collect valid license keys from ns_product_license
   • Call POST /API/AI/Token.php with license_keys and domain
   • Store the Bearer token (encrypted)
   • Set credit_mode = 1
   • Load balance from the T3Planet API
3. On success:
   • Toast: Credits mode is active.
   • Page reloads
   • Credits dashboard shows balance, plan, and bundles

​

Step 5 — Verify in the backend UI

• Provider mode — T3Planet Credits selected with ACTIVE badge.
• Provider list — Read-only; banner that local providers are preserved but not used.
• Dashboard — Credit balance visible (not “Activate to load balance”).
• Buy Credits tab — Bundles load when the API is reachable.
• AI Usage log — After an AI action: provider t3planet_credits, status success, credits debited.

​

Step 6 — AI smoke test

1. Run any T3AI feature (translate content, SEO meta, MCP native tool, …)
2. Open AI Usage and confirm:
   • Provider: t3planet_credits
   • Status: success
   • Credits debited

​

Part C — MCP testing (optional)

​

Step 1 — Set MCP mode to Native

1. T3AF → MCP Server
2. Set mode to Native (not Context)
3. Confirm MCP mode saved. and refresh to verify persistence

​

Step 2 — Connect MCP client

​

Step 3 — Check tool schema

• aiProvider — Dropdown shows t3planet_credits only.
• Description — States that T3Planet Credits mode is active.

​

Step 4 — Run tool and verify log

​

Part D — Switch back to Your Own API Keys

1. AI Providers → Your Own API Keys → confirm switch
2. Configure at least one connected provider (API key + Test connection)
3. MCP Native tools should list local providers in aiProvider
4. AI Usage should show the local provider identifier, not t3planet_credits

​

Part E — Troubleshooting

• Activate: “No T3Planet license keys found” — No valid ns_product_license rows. Activate T3Planet extension licenses in TYPO3 first.
• Activate: API / network error — Cannot reach composer.t3planet.cloud. Fix outbound HTTPS and retry Activate.
• Toggle ON but no balance / “click Activate” — Token not minted. Click Activate (toggle alone is insufficient).
• Credits “on” but AI uses local provider — Credits not fully active (no token). Re-run Activate; check tx_nst3af_runtime_setting.
• MCP lists openai-1, mistral-… in aiProvider — Credits not active or stale MCP schema. Confirm ACTIVE plus balance; flush caches; reconnect MCP client.
• Domain / license errors from API — Hostname not on license. Register DDEV or staging domain on the T3Planet license.
• AI fails: proxy unreachable — Credits ON but API unreachable. Fix connectivity or switch to Your Own API Keys temporarily.

​

Optional DB check (dev/QA)

SELECT credit_mode,
       license_keys,
       CASE WHEN token_enc != '' THEN 'yes' ELSE 'no' END AS has_token
FROM tx_nst3af_runtime_setting
WHERE uid = 1;

​

Part F — QA checklist

[ ] ns_t3af + child extensions installed and active
[ ] nitsan/ns-license present; valid key(s) in ns_product_license
[ ] Outbound HTTPS to composer.t3planet.cloud works
[ ] Backend: T3Planet Credits selected
[ ] Backend: Activate clicked → success toast + reload
[ ] Balance visible on dashboard
[ ] Provider list read-only under credits mode
[ ] One backend AI action → AI Usage shows t3planet_credits
[ ] (MCP) Native mode saved on MCP Server tab
[ ] (MCP) Tool schema shows t3planet_credits only in aiProvider
[ ] (MCP) Native tool call → credits debited in AI Usage log
[ ] Switch to Your Own API Keys → local providers usable again

​

Summary

1. License first — valid T3Planet keys in TYPO3
2. AI Providers → T3Planet Credits
3. Click Activate (mandatory)
4. Confirm balance and ACTIVE
5. Smoke-test AI → log must show t3planet_credits
6. For MCP: Native mode + aiProvider = t3planet_credits