> For the complete documentation index, see [llms.txt](https://docs.taco.build/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taco.build/reference/architecture/porter.md).
# Porter
## Overview
Porter can be described as the *“Infura for TACo”*. Porter is a web-based service that performs TACo-based protocol operations for applications.
Its goal is to simplify and abstract the complexities surrounding the TACo protocol to negate the need for applications to interact with it via a Python client. Porter introduces the TACo protocol to cross-platform functionality, including web and mobile applications.
Any publicly available Porter instance can be used to interface with the TACo nodes, or some application developers opt to [run their own](https://github.com/nucypher/nucypher-porter).
## Public Porter Instances
Public Porter instances are operated by centralized entities and have different security properties than user-operated instances.
To use the default Porter URIs in `taco`:
```typescript
import { domains, getPorterUri } from '@nucypher/taco';
const porterUri = getPorterUri(domains.MAINNET); // mainnet
// OR
const devPorterUri = getPorterUri(domains.DEVNET); // lynx testnet
```
Alternatively, you can use your own non-default Porter URIs.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.taco.build/reference/architecture/porter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
