Access, allowances and costs
A capability in the public catalog is a platform offering, not proof that your business can use it immediately. Your agent should verify the project, required permissions, service allowance and any provider-account setup before committing to the work.
Credentials have different jobs
Section titled “Credentials have different jobs”The local agent uses the project’s private key for authorized API operations. Limited-permission keys can provide narrower access to additional tools; creation and revocation follow the API access instructions.
Deployed applications receive a separate product-runtime identity from Egbe hosting. Keep the agent key out of product source, browser code and deployment configuration. A founder-approved connector also has its own connection lifecycle; use Dashboard to review or disconnect connected assistants.
Check the relevant allowance
Section titled “Check the relevant allowance”The installed request helper can read GET /me/limits. Its response identifies the business and describes each resource’s unit, usage, allowance and reset period. Follow the usage instructions.
An allowance of zero with zero usage means the action is unavailable, not exhausted. Daily and monthly limits use their returned reset times; inventory limits do not reset on a calendar. A missing custom-domain allowance, for example, does not remove ordinary .egbe.app publishing.
Some providers require separate readiness checks. New Google Ads work needs an assigned or approved account; a Dashboard OAuth connection alone does not establish that assignment. Use the capability’s current instructions instead of assuming that possession of a project key enables every service.
Budget from current Wallet policy
Section titled “Budget from current Wallet policy”Ask your agent to read both GET /wallet/balance and GET /wallet/policy through the installed helper. The Wallet instructions explain available funds, reserved amounts, periodic project fees, metered usage and the current commercial pricing fields.
A positive balance is not a complete estimate of how long a customer-facing service can operate. Due fees and reconciliation of incurred usage can exceed a small available balance; the Wallet is not a hard spending cap. Retention and grace conditions come from the actual policy and project state, not a generic promise.
Agree a total budget and permitted activities before paid work. Your agent should include applicable usage fees in estimates, recheck spending at meaningful points and stop before exceeding your authorized amount. An authorized task does not authorize a top-up or an unrelated advertising purchase.
Use Dashboard for the owner’s normal funding or recovery flow. Consult the current commercial terms for sales, top-ups, payouts, refunds and responsibilities. Product revenue and payment processing remain separate from the Wallet used to operate the business.