Planbwander

Created By
imismailpea year ago
Find interesting things to explore in a place with the help of AI
Overview

What is Planbwander?

Planbwander is an AI-powered tool designed to help users discover interesting places and activities to explore in various locations.

How to use Planbwander?

To use Planbwander, simply run the development server using npm, yarn, or other package managers, and access the application through your browser at http://localhost:3000.

Key features of Planbwander?

  • AI-driven recommendations for places to explore
  • User-friendly interface built with Next.js
  • Easy setup and deployment on Vercel

Use cases of Planbwander?

  1. Finding local attractions while traveling
  2. Discovering hidden gems in your city
  3. Planning weekend getaways based on user interests

FAQ from Planbwander?

  • Can Planbwander be used for any location?

Yes! Planbwander can provide recommendations for various locations worldwide.

  • Is there a mobile version of Planbwander?

Currently, Planbwander is designed for web use, but a mobile version may be developed in the future.

  • How does Planbwander generate its recommendations?

Planbwander uses AI algorithms to analyze user preferences and location data to suggest relevant places.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
imismailpe
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago