Set up periodic or one-time scheduled events via an x402-paid agent on Base Sepolia.
What it does
Schedule Master is an AI agent endpoint hosted on Questflow's infrastructure that helps users configure periodic or one-time scheduled events. It accepts natural-language instructions via a simple POST request with an `input` string field and returns a text response from the agent. Use cases include setting up daily system monitoring checks, weekly report triggers, time-specific action scheduling (e.g., "every day at 3 PM"), and recurring task automation.
The endpoint is gated by the x402 payment protocol (version 1) on the Base Sepolia testnet. Each request costs up to 500,000 units of USDC (the testnet USDC token at 0x036CbD53842c5426634e7929541eC2318f3dCF7e), with a maximum timeout of 1200 seconds. Payment is sent to 0x8702eFb89e3FC8A57BF175FA244C84cDAb0c6A5C. Because this runs on Base Sepolia, it is a testnet/development deployment and not suitable for production workloads.
No OpenAPI spec, dedicated documentation, or usage examples are published. The input/output schema is minimal: send a JSON body with an `input` string and receive a JSON object containing a `response` string. The broader Questflow platform focuses on autonomous AI agents for onchain market operations, but this particular endpoint is a standalone scheduling utility agent.
Capabilities
Use cases
- —Setting up daily system monitoring checks via natural language
- —Scheduling weekly report generation triggers
- —Creating one-time reminders or actions at a specific date and time
- —Configuring recurring tasks like data backups or notifications
- —Triggering time-based operations in automation workflows
Fit
Best for
- —Developers experimenting with x402-paid agent APIs on testnet
- —Simple natural-language scheduling without building cron infrastructure
- —Prototyping automated recurring task workflows
Not for
- —Production scheduling requiring guaranteed uptime and SLAs (this is a testnet deployment)
- —Complex workflow orchestration with branching logic or dependencies
- —Free or unauthenticated scheduling needs
Quick start
curl -X POST \
https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:683984b8ec15a7b81ce4a4ac \
-H 'Content-Type: application/json' \
-H 'X-PAYMENT: <x402_payment_header>' \
-d '{"input": "Schedule a daily system health check at 9 AM"}'Example
Request
{
"input": "Schedule a weekly report every Monday at 8 AM"
}Response
{
"response": "Scheduled: weekly report every Monday at 8:00 AM. Your recurring event has been created successfully."
}Endpoint
Quality
No OpenAPI spec, no documentation pages (all return 404), no usage examples, and the endpoint runs on Base Sepolia testnet only. The only concrete information comes from the x402 challenge payload and the existing description. The response example is entirely inferred.
Warnings
- —Testnet deployment only (Base Sepolia) — not suitable for production use
- —No API documentation available; /docs, /api, /pricing, /README all return 404
- —Output schema and response format are inferred from minimal x402 challenge metadata
- —maxAmountRequired of 500000 USDC units — actual cost in real terms is unclear on testnet
- —No SLA or uptime guarantees documented
Citations
- —Endpoint uses x402 version 1 payment protocol on base-sepolia network with maxAmountRequired of 500000https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:683984b8ec15a7b81ce4a4ac
- —Payment asset is USDC at address 0x036CbD53842c5426634e7929541eC2318f3dCF7e, payTo 0x8702eFb89e3FC8A57BF175FA244C84cDAb0c6A5Chttps://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:683984b8ec15a7b81ce4a4ac
- —Input schema accepts a POST with a string field 'input'; output returns a string field 'response'https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:683984b8ec15a7b81ce4a4ac
- —Questflow platform focuses on autonomous AI agents for onchain market operationshttps://api-dev.intra-tls2.dctx.link