← Back to Skills Marketplace
justoneapi

Beike API

by justoneapi · GitHub ↗ · v1.0.10 · MIT-0
cross-platform ✓ Security Clean
209
Downloads
0
Stars
1
Active Installs
11
Versions
Install in OpenClaw
/install justoneapi-beike
Description
Analyze Beike workflows with JustOneAPI, including resale Housing Details, resale Housing List, and community List.
README (SKILL.md)

Beike

This skill wraps 3 Beike operations exposed by JustOneAPI. It is strongest for resale Housing Details, resale Housing List, and community List. Expect common inputs such as cityId, condition, houseCode, limitOffset, offset.

When To Use It

  • The user needs resale Housing Details or resale Housing List on Beike.
  • The task lines up with community List rather than a generic cross-platform workflow.
  • The user can provide identifiers or filters such as cityId, condition, houseCode, limitOffset.
  • The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

  • ershoufangDetailV1: Resale Housing Details — Get Beike resale Housing Details data, including - Pricing (total and unit price), Physical attributes (area, and layout, for displaying a full property profile to users and detailed price comparison between specific listings
  • getErshoufangListV1: Resale Housing List — Get Beike resale Housing List data, including - Supports filtering by city/region, price range, and layout, for building search result pages for property portals and aggregating market data for regional housing trends
  • communityListV1: Community List — Get Beike community List data, including - Community name and unique ID and Average listing price and historical price trends, for identifying popular residential areas in a city and comparing average housing prices across different communities

Request Pattern

  • 3 operations are available in this skill.
  • HTTP methods used here: GET.
  • The most common non-token parameters are cityId, condition, houseCode, limitOffset, offset.
  • All operations in this skill are parameter-driven requests; none require a request body.

How To Work

  1. Read generated/operations.md before choosing an endpoint.
  2. Start with one of these operations when it matches the user's request: ershoufangDetailV1, getErshoufangListV1, communityListV1.
  3. Pick the smallest matching operation instead of guessing.
  4. Ask the user for any missing required parameter. Do not invent values.
  5. Call the helper with:
node {baseDir}/bin/run.mjs --operation "\x3Coperation-id>" --token "$JUST_ONE_API_TOKEN" --params-json '{"key":"value"}'

Environment

  • Required: JUST_ONE_API_TOKEN
  • This skill uses JUST_ONE_API_TOKEN only for authenticated Just One API requests.
  • Keep JUST_ONE_API_TOKEN private. Do not paste it into chat messages, screenshots, or logs.
  • Get a token from Just One API Dashboard.
  • Authentication details: Just One API Usage Guide.

Output Rules

  • Start with a plain-language answer tied to the Beike task the user asked for.
  • Include the most decision-relevant fields from the selected endpoint before dumping raw JSON.
  • When using ershoufangDetailV1, explain why the returned fields answer the user's question.
  • If the user gave filters such as cityId, condition, houseCode, echo those back so the scope is explicit.
  • If the backend errors, include the backend payload and the exact operation ID.
Usage Guidance
This skill appears to do exactly what it says: run a small Node CLI that queries JustOneAPI's Beike endpoints using JUST_ONE_API_TOKEN. Before installing, consider: (1) Keep JUST_ONE_API_TOKEN secret and do not paste it into chats or logs; (2) the token is sent as a query parameter by the included CLI — query strings can be recorded in server logs, proxies, or browser history, so prefer issuing a token with limited scope or request that the provider accept header-based auth; (3) verify api.justoneapi.com and the Just One API dashboard are the expected vendor endpoints; (4) monitor token usage on the Just One API dashboard and rotate the token if you suspect leakage. If you need confirmation of network behavior, review the included bin/run.mjs file (it performs only HTTP GET requests to the documented endpoints and writes the JSON response to stdout).
Capability Assessment
Purpose & Capability
Name/description, required binary (node), and the single required env var (JUST_ONE_API_TOKEN) all match a simple API wrapper for JustOneAPI's Beike endpoints. The included operations (communityListV1, ershoufangDetailV1, getErshoufangListV1) and base URL point at api.justoneapi.com as expected.
Instruction Scope
SKILL.md instructs the agent to select an operation, ask for missing parameters, and run the included Node CLI which performs HTTP GETs to the declared baseUrl. The instructions do not ask the agent to read unrelated files, access other env vars, or exfiltrate data to unexpected endpoints. One implementation detail: the API token is sent as a query parameter (token) rather than an Authorization header, which can expose the token in logs or URLs — this is a security note but not incoherent with the skill's purpose.
Install Mechanism
There is no install spec (no external downloads). The skill is delivered as a small self-contained Node script (bin/run.mjs) and generated OpenAPI artifacts. No remote installers, shorteners, or archive extraction are used.
Credentials
Only one environment variable is required (JUST_ONE_API_TOKEN), and that is the declared primary credential for authenticating to JustOneAPI. No unrelated secrets, system config paths, or multiple unrelated credentials are requested.
Persistence & Privilege
The skill does not request always:true and makes no changes to other skills or system-wide configuration. It runs on demand/autonomously per platform defaults, which is expected for a callable API skill.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install justoneapi-beike
  3. After installation, invoke the skill by name or use /justoneapi-beike
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.10
- Updated generated/operations.json and generated/operations.md to reflect latest API details. - No changes to user-facing endpoints or core workflow. - Documentation remains unchanged except for possible updates from generated sources. - Internal operation reference and metadata refreshed to stay current with API specifications.
v1.0.9
- Updated the Just One API Usage Guide link to include UTM parameters for improved referral tracking. - No functional or API changes; documentation only.
v1.0.8
- Updated the Just One API Dashboard link to include UTM parameters for tracking. - No changes to functionality or usage; documentation only.
v1.0.7
justoneapi-beike v1.0.7 - Clarified usage of `JUST_ONE_API_TOKEN` in the Environment section: now explicitly states it is only for authenticated Just One API requests. - No functional or API changes; documentation update only.
v1.0.6
Version 1.0.6 - Added a note to keep the `JUST_ONE_API_TOKEN` private and not share it in chats, screenshots, or logs. - No other logic or functionality changes; documentation improved for security awareness.
v1.0.5
Version 1.0.5 - Added explicit instructions on how to obtain a required API token, including links to the Just One API Dashboard and usage guide. - Environment section expanded to clarify authentication and onboarding steps. - No functional or operational changes to endpoints or logic.
v1.0.4
rename
v1.0.3
- Updated the skill display name in SKILL.md from "justoneapi_beike" to "Beike API" - No other changes; functionality, endpoints, and usage instructions remain the same
v1.0.2
justoneapi-beike 1.0.2 - Expanded and clarified documentation to highlight support for 3 specific operations: resale Housing Details, resale Housing List, and community List. - Updated SKILL.md with concrete input parameter guidance and representative usage scenarios. - Revised output instructions to better emphasize relevant response fields and explicit error handling. - Operations and request patterns are now detailed for easier integration and usage.
v1.0.1
- Added the --token "$JUST_ONE_API_TOKEN" flag to the node command in usage instructions. - Updated documentation in SKILL.md to reflect this required token usage. - No functional changes to API operations.
v1.0.0
Initial release of the justoneapi-beike skill. - Enables access to JustOneAPI Beike endpoints using HTTP APIs. - Supports raw API output plus a structured summary. - Guides users to select the appropriate endpoint and provide required parameters. - Requires the JUST_ONE_API_TOKEN environment variable for authentication.
Metadata
Slug justoneapi-beike
Version 1.0.10
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 11
Frequently Asked Questions

What is Beike API?

Analyze Beike workflows with JustOneAPI, including resale Housing Details, resale Housing List, and community List. It is an AI Agent Skill for Claude Code / OpenClaw, with 209 downloads so far.

How do I install Beike API?

Run "/install justoneapi-beike" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Beike API free?

Yes, Beike API is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Beike API support?

Beike API is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Beike API?

It is built and maintained by justoneapi (@justoneapi); the current version is v1.0.10.

💬 Comments