Parlo

Guides

API connections

Connect documented APIs as folders of readable, editable resources.

Parlo mounts documented APIs as folders.

bash3 lines
1ls ~/parlo/github/issues/2cat ~/parlo/linear/ENG-123.md3vim ~/parlo/github/issues/42.md

API resources become markdown files. Reading a file calls the API. Saving a file can update the remote resource.

Connect from a provider or intent

You can choose a provider:

bash3 lines
1GitHub2Stripe3Linear

Or describe what you want:

bash3 lines
1API for wrestling matches2weather alerts API3restaurant health inspection API

Parlo searches for real API documentation, asks what you want mounted, generates an adapter, and tests it before saving.

How generation works

  1. 1Find official docs, specs, schemas, or examples.
  2. 2Ask which resources should appear as files.
  3. 3Generate a filesystem adapter for that scope.
  4. 4Ask for your API key only when ready to test.
  5. 5Run the adapter in a sandbox.
  6. 6Save the connection if the test passes.

Generated adapters

A generated adapter translates file operations into API calls.

File actionAPI behavior
lslist resources
catfetch and format a resource
save / writecreate or update
rmdelete, close, or clean up

Adapters are generated from documented APIs. If Parlo cannot find enough information, it asks for a docs URL or another provider instead of guessing.

Credentials

The wizard does not ask for an API key up front. It asks only when the adapter is ready to run a sandbox test. Saved credentials are encrypted and injected by Parlo at runtime.

Example shapes

A project management API might look like:

bash4 lines
1~/parlo/linear/2  README.md3  ENG-123-fix-login.md4  ENG-124-update-billing.md

A search API might look like:

bash4 lines
1~/parlo/search/rust-vs-go/2  README.md3  1-rust-vs-go-performance.md4  2-when-to-use-rust.md
← Previous

Filesystem model

Next →

Cloud drives