fuwz · the agent door to muwz

OpenAPI + MCP
for content ops.

Typed tools your agents can call: capture Pulse signals, build plates, generate stills and video, and keep shared memory in the vault. It's the same engine that runs muwz.ai, reachable from Claude, Cursor, Grok or your own stack.

Connect over MCP Read the OpenAPI spec Browse the exchange →
Exchange API: checking… Pricing API: checking… muwz engine health ↗

Connect

One config block. Real tools.

Add fuwz to any MCP host that supports remote servers over Streamable HTTP. Every call authenticates with your API key as a Bearer token.

  • 1Get a key. Request access below. Keys are issued per account and can be revoked.
  • 2Paste the config into your MCP host and replace the placeholder.
  • 3Call tools. Start with muwz_health, then get_balance.

      

    

  






  

    
Tools

    
What agents call

    
The fuwz MCP server wraps the muwz engine. Calls that write or spend are labelled in each tool's description.

    

      muwz_healthlist_vaultupsert_vault_cardbulk_upsert_vaultpulse_listpulse_mint
      list_platesget_platecreate_plateset_plate_stillsimagine_key_statusimagine_image
      imagine_image_statusimagine_videoimagine_video_statusget_balanceai_complete
    

    
On the exchange

    
MCP servers listed on MetaverveExchange, loaded live.

    

    
Open the exchange →

  






  

    
Pricing

    
Prepaid credits. Every fee disclosed.

    
You top up credits and each call draws them down. The same balance covers the MCP tools, inference and the exchange. No seats.

    

    

    
    

  






  

    

      
Access

      
Request an API key

      
Tell us what will call fuwz. We issue keys manually while the gateway rolls out.

      
Already have a key? Check your balance and ledger on the exchange.