BDK Native status
Answered our latest tool-list check 3 hours ago with 11 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:16 | Answered | 1.9 s | 11 |
| 16 Nov, 06:15 | Answered | 1.6 s | 11 |
Tools (11)
Read from the server on 17 Nov 2026.
- bdk_whoami
- Read the signed-in user and their projects, with the project codes the other tools take. product_selected can be an unconfirmed default. Legacy status is not ledger entitlement; bdk_next.commerce has the entitlement.
- bdk_projects
- List projects or read a status/progress/health snapshot, not full settings or credentials. Use bdk_next.commerce for ledger entitlement and current requests. Do not infer payment or delivery from legacy status, paid_for_service, requested_build, build_complete, rebuild_credits or free_rebuild_expires_at.
- bdk_next
- Read workflow state and next steps; call again after each action. confirm_product writes and records the customer-confirmed iOS / Android / Both choice: ask first. Checkout requires recorded confirmation matching the saved platform, even when the saved default already matches the customer's choice. If confirmation is missing or mismatched, send the answer as confirm_product, then re-read. A purcha
- bdk_create_project
- Create a project after approval of the reference label and published app URL. project_name is a reference label, not the home-screen app name; that starts as the website hostname until configured. Duplicates by reference label or site host return candidates: ask the customer to choose create_new or use_existing with project_code; never reuse automatically. For an owner preview, pass from_preview_i
- bdk_configure
- Change a project's settings after the customer approves each value. Writable keys: app_name, launch_link, product_selected, statusbar_color, push_prompt_mode, push_enabled, app_icon_link, app_orientation_ios, app_orientation_android, app_tracking_ios, background_audio_ios, background_location_enabled_android, location_precision_android, target_devices_ios, message_apptracking, message_camera, mess
- bdk_upload
- Import a direct public HTTPS PNG, JPEG or WebP image up to 8 MB, without redirects; this does not assign a screen. Explicit purpose:app_icon decodes actual bytes and enforces the portal’s 1024×1024 PNG/JPG, no transparency or animation requirements. Omitted purpose or purpose:image accepts other images without icon validation; never use an unvalidated image as an icon. Use the portal for local fil
- bdk_setup_preview
- Creation requires intent:new; legacy app_link + preview_id updates that selected preview. list returns account preview names, published URLs, IDs and creation times. new calls the portal preview-manage create path (same-URL reuse and 20-preview cap); update requires the customer-selected preview_id and replaces that link. Published-link checks reject editor and builder-share links. At cap: Delete
- bdk_estimate
- With project_code, verify access and read ledger offers; report lookup failure rather than substituting a standard quote. A legacy project without product returns legacy_project; with product, it returns standard prices. Without project_code, product also selects standard prices, not eligibility. offer.unit_amount is in minor units of currency. The tool never creates a payment URL. BDK builds and
- bdk_check
- Read health checks and health_checked_at, not build execution status. run:true schedules an asynchronous check: use it when no snapshot exists yet, after the customer changed screens or credentials on the portal, or when the customer asks for a new check; otherwise read without run. If scheduled, re-read without run after a minute. If not scheduled, say so and use the portal. A passing check is an
- bdk_checkout
- Creates a Stripe-hosted checkout page that the customer reviews and pays on themselves; this tool never charges, never sees card details and never completes a payment. Start or poll a project purchase only after purchase approval. First read bdk_next.commerce and confirm the customer’s platform via bdk_next confirm_product; a default Both is not consent. Checkout requires recorded platform confirm
- bdk_build
- Request a build or rebuild only after explicit approval of that request and the saved settings. A first build requires confirm_build:true after the customer says yes. A ledger rebuild consumes one banked rebuild: pass build_kind:rebuild and confirm_consumes_rebuild:true. free_rebuild is legacy-only. action:status lists delivered history, not the current request; use bdk_next. action:download retur