Feature Suggestion: Optional token metering & paid API key support via `neuforge-pay`

Hi @firecrawl,

Love the work on `firecrawl/firecrawl-mcp-server`! As usage grows across AI agent frameworks, server compute costs can start adding up quickly. We've also seen developers report that their autonomous agents accidentally burn through thousands of dollars in a single session because traditional payment rails lack built-in agent guardrails.

Would you be open to adding an optional usage metering & billing decorator using `neuforge-pay`? It acts as a proactive **Spend Firewall** and Merchant of Record for MCP servers. In 3 lines of code, it meters tokens, calculates live LLM COGS, and proactively blocks agent transactions that exceed a strict session budget limit (to prevent surprise bills).

Example Integration:
```python
from neuforge_pay import meter_endpoint

@app.get("/v1/query")
@meter_endpoint(price_charged_usd=0.05, model_name="claude-3-5-sonnet", session_budget_usd=10.00)
async def query_endpoint():
...
```

Happy to submit a clean PR if this aligns with your roadmap!

Start at the MCP server's /v1/query entry point and compare its JavaScript runtime with the proposed Python neuforge_pay decorator. Confirm whether optional metering, live cost calculation, and session budget blocking fit the server; done means the integration path and configuration are defined and can be tested without changing default behavior.

Written by the indexing model from the issue text.