Apify MCP server drops legacy SSE transport for streamable HTTP and adds agent payments

The Apify MCP server at mcp.apify.com has migrated its transport layer: the old https://mcp.apify.com/sse endpoint is gone, replaced by streamable HTTP, so client configs must remove the /sse suffix and point at https://mcp.apify.com. The hosted version alone can infer output schemas, turning structured Actor results into usable schemas, a feature unavailable when running locally over stdio. The default toolset includes search-actors, fetch-actor-details, and call-actor, with apify/rag-web-browser and apify/web-fetch Actors preloaded. On payments, three agent channels were added: AGI pays via x402 or MPP in exchange for prepaid, capped Apify API tokens usable with any Actor; direct x402 settles per request in USDC on Base, requiring an mcpc client that supports the protocol; Skyfire uses PAY tokens with a $5 minimum, passing skyfire-pay-id explicitly in call params. Both direct methods are limited to event-billed Actors, not resident ones, settling per run rather than minting tokens. The impact lands on two groups: developers wiring Apify into MCP clients like Claude Code, Claude.ai, Cursor, and VS Code must update configs now to migrate transport; and teams building autonomous agents that want to pay for scraping runs without an Apify API token can go through AGI or x402, accepting the event-billed-Actor and per-run settlement limits.